Home › Forums › Archived Forums › Mobile View › Google Page Speed, Mobile View & Cache Issue
- This topic has 4 replies, 2 voices, and was last updated 6 years, 8 months ago by
Rinaldo.
-
AuthorPosts
-
September 27, 2016 at 17:23 UTC - Views: 54 #19597
Rinaldo
ParticipantHi,
Since Google ranks speedy mobile views higher I invested some time to make the Weaver Pro Mobile View faster.
I have the following issue:
When I do a Google Page Speed test of http://irinaafrica.tours/ the first time, the Google rating is 85/100 and I see my Mobile home page. When I do it a second time, I get 55/100 and see my Desk Top home page.When I wipe the Comet cache, I am back to 85/100 and see my Mobile home page.
To the 55/100 rate Google comments- …emes/weaver-ii-pro/style-minimal.min.css
- …hemes/weaver-ii-pro/style-mobile.min.css
is blocking the rendering.
I also tried another cache plugin with a separate cache for Mobile, with the exactly same result.Apparently the user gets the Desk Top home page delivered when visiting the home page a second time. Any ideas why this happens?
Thank you!
September 27, 2016 at 17:32 UTC - Views: 6 #30887scrambler
ModeratorFirst thing you should do is switch to a Mobile responsive mode instead of a Mobile Smart mode.
Smart modes were there for antiquated compatibility , they are not compatible with most cache plugins, and are really not the way to go today.
Better yet, you need to move to Xtreme
But you know that 🙂
September 27, 2016 at 18:22 UTC - Views: 4 #30888Rinaldo
ParticipantHi,
Thanks for the prompt reply. Right, when I change to Responsive the problem is kind of solved, the speed rating is always 55/100. 😉 Because the Mobile Home page is not loaded
If you can guarantee that X would solve the issue I will invest the time and move.September 27, 2016 at 18:43 UTC - Views: 6 #30889scrambler
ModeratorThis does sound like a cache issues, and weaver II only supported a couple of specific cache plugins (documented in the help), but these may also have changed since then.
The way Xtreme works is supposed to be fully cache agnostic. You can easily switch to Xtreme momentarily to test what happens.
But clearly there will be no more support on Weaver II for this kind of things, so the way forward is Xtreme without a doubt.
There is a well documented conversion procedure below
September 27, 2016 at 19:25 UTC - Views: 8 #30890Rinaldo
ParticipantI like the “clone site” approach. Probably I could just re-map the domain to the new X site once the conversion is complete.
I am using a Child theme. Will that require more changes?
Thanks!
-
AuthorPosts
- The forum ‘ Mobile View’ is closed to new topics and replies.