Still extremely slow loading times for some assets

Hi,

Some weeks ago I reported this same problem about a personal site built with Publii here. Situation has not improved an inch since then. I attach a couple of HAR files.

HAR file 1
Request 1 (9.34s): x-nf-request-id: bb475d9b-20d0-402b-802d-87bd025ee636-39573782
Request 2 (10.08s): x-nf-request-id: bb475d9b-20d0-402b-802d-87bd025ee636-39573786

HAR file 2
Request 1 (22.78s): x-nf-request-id: 58ee76b9-d93b-4b08-a513-6434aee64cc2-14374849
Request 2 (46.32s): x-nf-request-id: 58ee76b9-d93b-4b08-a513-6434aee64cc2-14376895
Request 3 (44.01s): x-nf-request-id: 58ee76b9-d93b-4b08-a513-6434aee64cc2-14376894
(There are 3 more requests with 30+ seconds load time!)

NS Lookups against pablofelip.online show this (home, Ubuntu):

pablo@menos:~$ nslookup pablofelip.online
Server:		127.0.0.53
Address:	127.0.0.53#53

Non-authoritative answer:
Name:	pablofelip.online
Address: 165.227.12.111
Name:	pablofelip.online
Address: 2604:a880:2:d0::21e9:c001

Results show up instantaneously, as expected.

The problem manifests consistently at all times of day in:

  • Different devices: computers/OS, tablets, phone.
  • Different locations / ISP: home and office.
  • Different types of connections: wifi, wired, 4G.
  • Different DNS servers (Google, CloudFlare, standard one provided by ISP).

I am not using any kind of VPN. Web browsing (and any other network performance) is absolutely normal on my side.

I’ve tried deploying my site using Netlify’s URL (*.netlify.com) instead of my own domain with same results. A deployment against Github Pages is working flawlessly in the same test conditions.

Any idea about what could be going on here? Anything else I could try before dropping out?

Thank you very much in advance for your support and best regards.

Pablo

1 Like

Hi, @pfelipm. Are you perhaps using Cloudflare’s 1.1.1.1 DNS server? If so, this might be helpful:

I ask because the request is being made from an IP address in Spain to an IP address in the far western U.S.A. This is the most likely reason for the slow asset load.

For example, for the x-nf-request-id of “58ee76b9-d93b-4b08-a513-6434aee64cc2-14376894” this was an 8.6 MB file sent from San Francisco to Spain.

HTTP requests from Spain should be directed to a CDN node closer to you but the DNS server being used isn’t doing this. It is incorrectly returning an answer from another location.

My recommendation would be to change to a DNS service which correctly returns an IP address for your location. The DNS redirect to a closer CDN node works when I check with other third-party tools:

However, with your DNS server, it returns a California IP address to someone in Spain, which is incorrect.

Again, this is the exact issue being reported in the topic linked to above. The DNS service itself is causing the issue.

Would you change to a different DNS service (for your local resolver not the site domain name) and let us know your results?

Hi, Luke.

Yes, I am using Cloudflare’s DNS at home, but the problem arises in a very similar way at my office, with the standard ISP’s provided ones.

I’ve just changed my home DNS in the router to the ones provided by my ISP (Vodafone/Ono, 212.166.132.108, 212.166.132.96) and… nothing. The slowness is simply not acceptable for a simple, static personal blog. Some images keep coming up after 15 - 30+ seconds when the requests don’t hit the browser’s cache.

I understand the complexity of this DNS issues, but it is clearly not only affecting Cloudflare’s, and in any case this issue defeats for me, unluckily, the possibility of using Netlify as the hosting for my personal web as many people in Spain use Cloudflare’s service (I have no control over other user’s DNS setup).

Would this be different in case I chose one of your paid plans? I’d really like to stick with Netlify.

Hi, @luke, any update on this?

I understand the complexity of this DNS issues, but it is clearly not only affecting Cloudflare’s, and in any case this issue defeats for me, unluckily, the possibility of using Netlify as the hosting for my personal web as many people in Spain use Cloudflare’s service (I have no control over other user’s DNS setup).
Would this be different in case I chose one of your paid plans? I’d really like to stick with Netlify.

Hey @pfelipm,

Is there any chance that you could perform an nslookup from your locations, share the results and where you’re querying from exactly?

nslookup pablofelip.online 212.166.132.96

You can put your external-facing IP in to https://www.maxmind.com/en/geoip-demo and this will help us to determine where software thinks you are.

Hi, @Pieparker.

Here you are (@home):

nslookup pablofelip.online 212.166.132.96
Server:		212.166.132.96
Address:	212.166.132.96#53

Non-authoritative answer:
Name:	pablofelip.online
Address: 167.99.137.12
Name:	pablofelip.online
Address: 2a03:b0c0:3:e0::1b:1

Addresses change in almost each execution:
Address: 142.93.108.123
Address: 165.22.65.139
Address: 134.209.226.211
Address: 167.99.129.42
Address: 68.183.215.91
Address: 167.99.137.12
Address: 157.230.120.63

IP Address: 80.173.232.0/23
Country Code: ES
Location: Castelló de la Plana, Castellon, Valencia, Spain, Europe
Network: 80.173.232.0/23
ISP: Vodafone Spain
Organization: Vodafone Spain
Domain: ono.com

Hi,

I’m still in trouble with this issue.

and, my nslookup result

~> nslookup internalmeeting.com
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: internalmeeting.com
Address: 157.230.45.115

hey there, thanks for sharing that! We are still looking into this and haven’t forgotten about you - more soon.

1 Like

Hi there and sorry to be slow to diagnose! One of my teammates had done this research some time ago and it was my responsibility to close the loop and I did not.

What we can see from our internal logs on that specific request is:

  1. you made the request from a japanese IP address
  2. our nearest servers are in Singapore, and you were routed to one of them correctly (yay, not a DNS problem!)
  3. your asset was not in local cache on that node, so we fetched it from our data center in San Francisco
  4. we completed sending the asset in 498ms, well shy of the time to first byte shown in your HAR file.

Looking into the HAR analysis, the receiving takes FOREVER, and I think this is your problem:

specifically the “the bandwidth detected was too low” - your connection seems SEVERELY throttled on most of the requests.

Looking at the general logs for your site, I see over the past 30 days:

  • 115,326 requests total
  • about 4500 requests slower than 2 seconds on our server (from connection through transmission of last byte)
  • of those most (~3500) were for mobile user agents, where we might expect things to be slow.
  • average timing across all responses was around 500ms which isn’t great, but the average status of your assets is not-cached-on-a-cdn-node, so have to be transferred from the US data center to the local CDN node. Seems like most of your visitors are in Japan, so that will add a few hundred MS to prime the cache before the file can be served in many cases.

That’s as far as we’ll be able to debug things, but hopefully it let’s you make the business decision about whether that performance is suitable for your business at your $0 price point or not.