skip to Main Content

i am facing issue when i try to check or use any google tools (GTmatrix, PageSpeed Insights, Google Structure Data) to test my website. I got error

The page took too long to load

But when i test the same website on other tools like Pingdom Tools it showing good result, Result of last test (Page Load Time 1.5 Sec, performance A Grade, Request 24, Page size 1.3 MB).

I have VPS CentOS7, with Apache.

3

Answers


  1. This usually happens when your website scripts/plugins takes forever before the page is ready to be served. Try following:

    1. Add cache plugin(this will help in serving the page faster), or
    2. Disable scripts/plugins, test and verify which plugin is causing the issue. or
    3. Try serving a static page e.g. test.html and check if you get result for the page. If you indeed get pagespeed result than something is wrong with your website scripts/plugins.

    Edit #1
    A 15 second timeout has been introduced when considering the start of the page load. If your page doesn’t paint any content within ~15 seconds, Lighthouse will bail. This will result in the NO_FCP error.

    Login or Signup to reply.
  2. PageSpeed result is based on the combination of both real-world data and lab data. Some of the users may access your webpage from slow network or with old mobile devices. What you see is the average of the last 28 ​days. So even if you have taken improvement as James suggested, it takes time to see the change.

    Pingdom free webpage speed test does not have option on devices and network(3G/4G). I guess it tests from desktop devices.

    Login or Signup to reply.
  3. Two possible causes of this after running a performance trace:-

    Highly Likely – Total Blocking Time (TBT) cannot be calculated

    Lighthouse (the engine behind Page Speed Insights) never completes the Total Blocking Time test. For some reason you have a task that is permanently blocking the main thread, it appears to be something to do with animation so I would suggest removing the slider temporarily and then re running the test.

    For Lighthouse to complete it needs a gap where the CPU is not busy to calculate TBT, as this gap never comes it cannot complete and errors.

    Less likely – request never completes

    You have a request that never completes but also doesn’t through an error:- https://somivendors.com/cdn-cgi/rum?req_id=65e9be0aae4e542e, yet again this could be causing Lighthouse to fail as it never gets to a fully loaded state. I find this less likely to be the cause as it is only a ping but as it never resolves it could be causing a time out.

    Option 1 is where I would look (the slider or something to do with animation). I would also suggest you run a performance trace yourself and read how to interpret the results as you may be able to spot the problem more quickly as you know your code base (and can spend more time looking into it).

    Login or Signup to reply.
Please signup or login to give your own answer.
Back To Top
Search