Google mobile speed report - reposted 
Autor: Adrian B.
Visited 2721,
Followers 1,
Udostępniony 0
Sorry if this is a dupliacte - my same post earlier is set to private - not something I did I don't think?
Google has a mobile speed report available (https://testmysite.withgoogle.com/intl/en-gb).
When I run it with my website index page (abthermal.com) it reports:
"Resources for page styling and functionality are delaying visibility of primary content on the page. Deliver critical JS/CSS inline and defer all non-critical JS/styles."
So what is the plan for X5 to meet those recommendations?
Adrian
Posted on the
Hello.Try to find a hosting with Google Page Speed module support. As far as I know, here you can find this module:
Check the availability of this module in the technical support of the hosting provider.Pay attention to the fact that it may take you a long time to configure this module for your site.
(It > En) ... most of the problem and slowdowns consists of too many images of the slideshow, 22! for about 2 MB!
...
(... in my humble opinion, an expert would create a site suitable for the "mobile" device, separate from the Desktop site ...
... or create two external slideshows, extra, to be loaded into IFRAME based on the resolution, light for the "mobile" and normal for the "Desktop" ...
... but here is another matter and you need a minimum of personal preparation ...)
.
ciao
.
Autor
Thank you for your comments so far.
KolAsim - as I read the google explanation, the speed measurement is based on how long it takes the first content to load on the screen - not the total time to load all content.
As much research as I have done; it seems to point on how the page creation code (that is, X5) handles content management - independant of the size of the content.
Google seems to want sites to load "something" to keep user interest, and not wait for all resources to be loaded before displaying.
I am going to play with the content of the index page and see what happens...
Adrian
... to try, you can make a temporary test and test the test without the slideshow...
... for CSS files and JS files you can't do anything, whether not to take advantage of GZIP compression if it is supported by your server.
... in the case of a "mobile" site, the less you use effects and javascript, the better...
.
ciao
.
Autor
Stripped out all the index page gallery images - no change in load speed or google recommendations.
Disappointing
is X5 following google's recommendations for good site ranking?: Google suggests in the analysis:
Reduce JavaScript execution time (code tightness?)
Avoid an excessive DOM size (is that code or server side issue?)
Eliminate render blocking resources (is that code or server side?)
Serve static assets with an efficient cache policy (is that code or server side?)
... wait for the opinion of the experts ...
... but you will hardly find a site, not made exclusively for mobile, that answers 100% to the dictates of Google ...
ciao
.
Autor
Agreed....
But I have test sites with other authoring products, identical content, same server, that perform under the 1 second load time (3.5 seconds with x5 site), and without the suggested optimizations results.........
x5 has more design features and off-line build/edit capability, but at the price of a penalized performance .....
Adrian, perhaps this article will be useful to you: "Incomedia WebSite X5 speed optimization (tutorial part 16)".
Hi Adrian
The developers are always working in order to improve the way the software generates code to be able to provide the best score possible for all the mainstream services out there used for testing. Keep in mind that this might take time and is a job that is actually never done, since the web's requirement and ever-evolving and change incredibly fast.
The loading time you mentioned now is nothing to be particularly worried about in any case, plus from my tests, I can confirm that images are always what takes up the most time for loading, and in your case too.
In order to address the points you mentioned:
1_ Yes, this is indeed about code quality. Since no actual code quality verification can be done, this is more like of a general tip which should always be kept under consideration. This indicates no particular issue with anything
2_ This indicates that the page better not have too much material in it. This can also be achieved by the user by not overloading each page with elements.
3_ This is about what you mentioned initially. Do not include too much logic that delays the website's display.
4_ This is something that can be set server-side. Some content might be cached in order to load faster. You might need to manually refresh this cache on the server though if you need to update something on your website. Else, it might take time to display
I hope I've been helpful
Stefano