Hi @mskwarwsd
Thank you for response!
I’m really sorry that you are experiencing this issue and let me assure you that we’ll do everything in our powers to help with this. However, we first need to find out why it is happening in the first place and what is causing it – as it is not default or expected behavior and we do not have any known bugs related to this currently.
Even if it happens on more than a single page (as other person also mentioned it), it still must have some specific reasons which we need to identify to be able to replicate it and then – if it really is a bug, investigate and implement a fix; or – if it is something related to 3rd-party issues, find workaround.
—
That being said, I re-read your initial post and I think this part may be the key here: “Specifically, by broken, I mean it is displaying roughly mobile-width on desktop, and the navigation bar is 90% off-screen. The site is still functional, just not very usable.”
This suggests that the cached mobile version is served in every case. It’s not something Hummingbird would do “on its own” though. If it has Page Caching enabled, there is a setting in Page Cache settings called “Cache on mobile devices”.
With it enabled, there’ll be two different sets of cache created – separate for desktoip and separate for mobile devices. They’d be served based on WordPress core “wp_is_mobile()” function.
Now if it happens that it always serves this mobile (and additionally broken) version of page – even after clearing cache in Hummingbird – it suggests that
– either “something” on site is breaking or in other ways “affecting” this mobile detection
– or, more likely, there is some additional caching layer involved that’s not “in sync” with site/Hummingbird.
I believe you have considered that already but just to make sure: is there any server-side cache active (if yes, what kind)? Are you using any other caching and/or asset optimization plugins on site (if yes, what are they)? Is there any CDN (like CloudFlare or similar) integrated with you hosting plan and currently in use – if yes, what is that?
Kind regards,
Adam