PageSpeed Insights is a website benchmark tool offered by Google that evaluates the full analysis of web pages performance on both mobile and desktop devices. The tool offers a detailed report on various metrics that affects the website loading speed, such as:
- Core web vital assessment — Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS).
- Other notable metrics — First Contentful Paint (FCP), First Input Delay (FID), and the most significant one Time to First Byte (TTFB).
Those terms may sound difficult to understand, but they are just a detailed report on various performance metrics such as—identifies issues affecting load times, offers actionable recommendations to enhance page speed, and overall user experience.
But while testing a web page URL on PageSpeed Insights, very rarely we see an error that says — Unable to resolve {URL}. Checking the URL for validity. This makes us panic for a minute, but later confused as soon as you realize that in browser it is actually loading.
What is this issue, then?
Actually, there could be multiple reasons why we are facing this issue. I’ll explain what could be the main reason you are facing this, in high to low chance order.
High chance:
You have made some changes in DNS or Name Servers. Often bloggers and webmasters change some entry in DNS like A and AAAA record to cause this issue, but it resolves fast. But name servers may take more time, for example Cloudflare can cause multiple redirection issue if not configured correctly, and it ends up to the error.
If you are facing multiple redirection issues, then I will recommend checking the SSL certificate settings in Cloudflare and verify that it is set to full strict or not. If it is not, then set to full or full strict, then do it to solve the error.
I mentioned Cloudflare specifically because many bloggers and website owners use it as the CDN (Content Delivery Network) and WAF (Web Application Firewall) services.
Medium chance:
A firewall may have blocked something. Many bloggers and website owners use web application firewall that blocks any connection which continuously load the site.
If that is the case, then you know what to do next.
Low chance:
At last, ISP may fail to update DNS records for you. Possible fix is flush the DNS cache and restart the computer, and networking devices. Or you can switch to any free Public DNS like Google (8.8.8.8 and 8.8.4.4) and Cloudflare (1.1.1.1 and 1.0.0.1) which updates faster than your ISP’s DNS cache which stays stale for an hour to whole day.
Except firewall issue, all issues are resolved automatically in 24–48 hours, if the issue remains same, then check for the configuration and settings.
Leave a Reply