Lots of variables at play, @lukashavrlant! If you can provide an x-nf-request-id for a load time which you’re unhappy with, we can dig in. However, there’s a few reasons why requests may take “a bit longer” which fall in to two categories.
If you are using external DNS, ensure that you configure a subdomain (such as
www ) to be the primary domain in our UI. You should use a
CNAME record at your DNS provider for subdomain (such as
www). If you use Netlify DNS, you will not need to perform this as we will always route traffic via our CDN using
NETLIFYv6 DNS records.
In general, you may experience slow loads on our CDN, if a CDN node hasn’t cached the file before. In each region where we have a CDN presence, we have multiple nodes and they each have their own cache. If the node which responds to your request hasn’t cached the asset, the node must request the asset (uncompressed) from our west-coast US origin server. The asset is then sent uncompressed to the CDN node, compressed, then sent to the browser. This is a one-off longer load. Each node will preserve the asset until your site is re-deployed and the asset changes.
Other caveats (such as password protecting your site – either site-wide or using Basic-Auth – or fingerprinting your assets) will jeopardise how or whether we cache your content.
You can always check out our Statuspage for our service health.
It may be the case that your other site was smaller, and/or you were closer to the server than our CDN. You may be unfortunate and requesting assets which the CDN hasn’t cached (common for frequently deploying, low visitor sites – especially if files are hashed).
Again, feel free to provide an x-nf-request-id and we can see which of the above possible causes may be in effect.