Can't reach 100% in PageSpeed Insights due to Google tag manager

[Adam Peter Nielsen]

Google tag Manager and analytics are the only things that block ud from reaching a clean 100% in PageSpeed Insights.

Any ideas on how to fork around this?

We would like to use tag manager and analytics..

See attached screenshot.

Kind regards

Adam

[Carlos Lizaga Anadon]

Nothing can be done, the score means nothing but what can be improved and you cannot improve external JS resources cache so, basically, you will have to stick with that score or discard analytics and tag manager.

Regards.

[Adam Peter Nielsen]

It would be awesome with a cache setting in GTM and Analytics...

I can see how that would be an issue for google if they need to push new versions quickly. But would nonetheless be a nice feature.

/Adam

[Carlos Lizaga Anadon]

Analytics must work under any circumstance, that's why they keep low cache set, due to possible minor/major changes.

Making it remain more time in the client would cause inconsistency with API calls and make your site unable to communicate with analytics and causing data loss.

The solution is worse than the issue.

Regards.  

[Jonathan Garbee]

Please remember, you don't need a 100% score. 100% compared to 95% really doesn't get you much in most situations. So long as your *UX* is 100% (because we don't want people to have a bad experience with interaction), the speed is variable from project-to-project what is acceptable. So long as your are around 80%+, you are doing very well and that is very acceptable. Don't get caught up in needing 100% all the time, it isn't always applicable.

--
You received this message because you are subscribed to the Google Groups "pagespeed-insights-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pagespeed-insights-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pagespeed-insights-discuss/44b567c4-ead6-4001-a030-4bff720fa279%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Alice Wonder]

Also remember the score is just a number and is actually rather meaningless.

Two pages with identical issues - and I mean identical - one got 82% on usability and other got 93%. The difference - the 93% had gobs more content so even though it had the same identical errors, there was smaller error to content ration.
In reality the 82% was better UI because it was more concise and less scrolling.

So don't obsess over the numbers, they are just an automated thing and higher number doesn't mean the page is actually better than a page that scores lower.

[Rick Steinwand]

Also remember, tricks to make the score higher, might actually slow subsequent page load times (like inlining cacheable external files into the html).

[Carlos Lizaga Anadon]

Sounds like a reminded todo list, haha.