# Browsersync speed with .local

**URL:** <https://community.localwp.com/t/browsersync-speed-with-local/4090>\
**Category:** Support\
**Created:** [November 30, 2017, 9:39pm UTC](https://community.localwp.com/t/browsersync-speed-with-local/4090 "2017-11-30T21:39:24Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![zforsman](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/zforsman/32/1225_2.png) [@zforsman](https://community.localwp.com/u/zforsman)\
**Post date:** [November 30, 2017, 9:39pm UTC](https://community.localwp.com/t/browsersync-speed-with-local/4090/1 "2017-11-30T21:39:24Z")

</div>

I noticed after updating to 2.1.2 the default site url is using .local instead of .dev, cool.

The problem is that it doesn’t play nice with Browsersync on Mac. I noticed reload times upwards of 15 seconds every time I would save a sass file.

So I did some googling and came across this: [https://stackoverflow.com/a/45331805](https://stackoverflow.com/a/45331805)

Is this a known issue / is something being done about it, or should I continue to edit my hosts file after every new project creation with .local (or just go back to using .dev)?

Thanks!

---

<div class="post-metadata">

**Author:** ![clay](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/clay/32/8248_2.png) [@clay](https://community.localwp.com/u/clay)\
**Post date:** [November 30, 2017, 9:47pm UTC](https://community.localwp.com/t/browsersync-speed-with-local/4090/2 "2017-11-30T21:47:33Z")

</div>

Hi @zforsman,

Local 2.2.0 now automatically adds the IPv6 entries 🙂

See [Local by Flywheel 2.2.0 (Pre-release)](https://local.getflywheel.com/community/t/local-by-flywheel-2-2-0-pre-release/4089)

---

<div class="post-metadata">

**Author:** ![zforsman](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/zforsman/32/1225_2.png) [@zforsman](https://community.localwp.com/u/zforsman)\
**Post date:** [February 15, 2018, 7:02pm UTC](https://community.localwp.com/t/browsersync-speed-with-local/4090/3 "2018-02-15T19:02:47Z")

</div>

Hey @clay, I’m now on 2.2.3 and still seeing this issue. It’s still fixed by entering the IPv6 entries but this obviously isn’t ideal as every time a new project is added or stopped/started I have to redo them.

---

<div class="post-metadata">

**Author:** ![zforsman](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/zforsman/32/1225_2.png) [@zforsman](https://community.localwp.com/u/zforsman)\
**Post date:** [April 30, 2018, 1:41pm UTC](https://community.localwp.com/t/browsersync-speed-with-local/4090/4 "2018-04-30T13:41:51Z")

</div>

Ah ha! I see that this is an option in Preferences. I now have IPv6 entries for all my Local sites, yay! The option was off by default, which is not what I was expecting based on:

> Local 2.2.0 now automatically adds the IPv6 entries 🙂

That is indeed true, just make sure you have it turned on!

Thanks!

---

<div class="post-metadata">

**Author:** ![clay](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/clay/32/8248_2.png) [@clay](https://community.localwp.com/u/clay)\
**Post date:** [May 4, 2018, 9:00pm UTC](https://community.localwp.com/t/browsersync-speed-with-local/4090/5 "2018-05-04T21:00:13Z")

</div>

> [@zforsman](#):
>
> The option was off by default, which is not what I was expecting based on:

Understood! I’ll see if we can’t automate this in the future and have it add the loopback when necessary.

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/system/32/1_2.png) [@system](https://community.localwp.com/u/system)\
**Post date:** [August 25, 2020, 6:33pm UTC](https://community.localwp.com/t/browsersync-speed-with-local/4090/6 "2020-08-25T18:33:15Z")

</div>