Forum Moderators: open

Message Too Old, No Replies

Fetch and Render and Page Speed Insights don't like my new pages

         

NickMNS

2:43 pm on Mar 14, 2018 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



I just rolled out a big update of my main website. It is completely revamped from A-Z.

But when I run the pages through Fetch and Render, they do not render correctly, The menu along the top of the screen expands over the full screen. This is the case for both desktop and mobile. The fetch portion of the tool displays the source doe correctly. Page Speed insights also is unable to test the speed, it gives me good score for optimization but is unable to test the speed.

Testing in an actual browser shows everything works as expected. I tested, Chrome, Opera, Firefox, Safari and I have found no issues.
The website is live and has been running fine for the past three days, the user metrics do not suggest any issues.
The pages pass w3 validation (except for errors related AMP)
Chrome Lighthouse also shows everything is working correctly.

I am worried that there is some small technical issue or oversight that is going to cause me a disproportionately large impact in terms of indexing/rankings.

Need I be worried? Any ideas on what the issue might be?

robzilla

3:02 pm on Mar 14, 2018 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Did you test in some older browsers? Googlebot uses Chrome 42, for example.

it gives me good score for optimization but is unable to test the speed.

PageSpeed Insights does not test for speed. You only get a speed score if there's sufficient data for your site (mobile or desktop) in the Chrome User Experience Report dataset (updated weekly).

not2easy

3:08 pm on Mar 14, 2018 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



Have you tried out the validation tools:
HTML Validator: [validator.w3.org...]
CSS Validator: [jigsaw.w3.org...]

They generate a report that list any possible errors, along with "how to fix" notes. Validating isn't just for validating, it lets you see and decide what things might be important for users.

NickMNS

3:26 pm on Mar 14, 2018 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



I didn't test in an older versions of chrome, but there is nothing I'm using that should not work in Chrome 42. My least backward compatible feature is flexbox and that is documented to be supported by Chrome as of v29.

I think I know now what the issue may be. I haven't explicitly declared a height for my nav-menu and the div has fixed-position so the fact that it expands over the whole screen seems logically to suggest that this would be the issue. I am going to test it to see if it has an impact.

NickMNS

3:29 pm on Mar 14, 2018 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



@not2easy, I validated the HTML and everything checked out, the only errors where the AMP tags, which is obviously expected. I just tested the CSS and I got a perfect score.

NickMNS

3:39 pm on Mar 14, 2018 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Declaring the height fixed the issue!

Thanks for the help!

tangor

4:37 pm on Mar 14, 2018 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Another happy ending brought about by just asking a question and thinking it through,.

NickMNS

4:40 pm on Mar 14, 2018 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Sometimes, just taking the time to formulate a question with sufficient information and detail is enough to lead you to the answer.

keyplyr

10:18 am on Mar 15, 2018 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



"Our lives are defined by opportunities, even the ones we miss." - Benjamin Button