Slow speed to load
Post count: 24GuydeeJuly 2, 2018 at 5:10 am #33671
The website that I am using this code for is taking a very long time to load.
I have jnews speed and W3 Total Cache plugins activated.
Speed scores on GTMetrix and Google insights are OK but the time to first paint is poor.
Running an audit on Google Chrome gives a performance score of only 1% !!!Post count: 10687AdekJuly 2, 2018 at 11:19 am #33690
Can you provide your site URL for further testing?
Thank youPost count: 24GuydeeJuly 2, 2018 at 2:54 pm #33694Post count: 10687AdekJuly 3, 2018 at 9:35 am #33717
I’ve been checked your website previously and you may need to try enable minify HTML output option. You can setup it on the Customize > JNews Speed Option > HTML Option tab > Minify HTML output. It will help reduce the page size.
Thank youPost count: 24GuydeeJuly 3, 2018 at 2:30 pm #33761
Unfortunately, this has made no improvement to loading speed.
Chrome Audit report is as follows:
These encapsulate your web app’s current performance and opportunities to improve it.
These metrics encapsulate your web app’s performance across a number of dimensions.
Screenshot at 2.6 s
Screenshot at 5.2 s
Screenshot at 7.8 s
Screenshot at 10.5 s
Screenshot at 13.1 s
Screenshot at 15.7 s
Screenshot at 18.3 s
Screenshot at 20.9 s
Screenshot at 23.5 s
Screenshot at 26.2 s
First meaningful paint
First meaningful paint measures when the primary content of a page is visible. Learn more.
First Interactive (beta)
First Interactive marks the time at which the page is minimally interactive. Learn more.
Consistently Interactive (beta)
Consistently Interactive marks the time at which the page is fully interactive. Learn more.
Your page took too long to load. Please follow the opportunities in the report to reduce your page load time, and then try re-running Lighthouse. (NO_TTI_NETWORK_IDLE_PERIOD)
Perceptual Speed Index: 12,187
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Estimated Input Latency: 466 ms
The score above is an estimate of how long your app takes to respond to user input, in milliseconds. There is a 90% probability that a user encounters this amount of latency, or less. 10% of the time a user can expect additional latency. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
These are opportunities to speed up your application by optimizing the following resources.
Consider lazy-loading offscreen and hidden images to improve page load speed and time to interactive. Learn more.
Unused CSS rules
Remove unused rules from stylesheets to reduce unnecessary bytes consumed by network activity. Learn more
Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
More information about the performance of your application.
Uses inefficient cache policy on static assets: 4 assets found
Critical Request Chains: 2
Main thread work breakdown: 30,700 ms
Avoid invisible text while webfonts are loading
12 Passed Audits
Generated by Lighthouse 2.9.1 on Jul 3, 2018, 7:26 AM GMT+1 | File an issuePost count: 10687AdekJuly 4, 2018 at 11:42 am #33788
For Google Chrome Audit, we’re not making optimization yet. We will take a look at this thing.
Also, please try to use WP Super Cache instead of W3 Total Cache plugin and check the result.
You must be logged in to reply to this topic.