HOTEL & RESTAURANT
WEBSITE GRADER

What the grader checks

Enter a URL and the grader runs it through Google's PageSpeed Insights API, the same Lighthouse engine behind Google's own PageSpeed report. It runs the mobile strategy and the performance category, so the result reflects a phone rather than a desktop.

You get an overall letter grade from A to F, a performance score out of 100, a count of issues found, First Contentful Paint, Largest Contentful Paint, an HTTPS check and a mobile-friendly check, plus up to five prioritised recommendations. No signup, no email address. Analyses are limited to five per ten minutes from the same connection.

What the speed metrics mean

First Contentful Paint is the moment anything from your page appears. Largest Contentful Paint is the moment the biggest element in view has finished loading, usually a hero image or a heading block. Those are the two timings the report puts on screen. LCP is the one to prioritise: it is a Core Web Vital and FCP is not. Google treats 2.5 seconds or less as good and over 4 seconds as poor. The grader counts an LCP over 2.5 seconds, or an FCP over 1.8 seconds, as an issue.

Two more metrics sit behind the score rather than on the report. Cumulative Layout Shift measures how much the page moves under the reader while it loads: the image that arrives late and shunts the button down. 0.1 or less is good, above 0.25 is poor. Total Blocking Time measures how long the main thread was too busy running JavaScript to answer a tap. It is the lab stand-in for Interaction to Next Paint, the metric Google records on real visits, where 200 milliseconds or less is good.

How the letter grade is worked out

The letter comes straight from the Lighthouse performance score. 90 and above is an A, 80 to 89 a B, 70 to 79 a C, 60 to 69 a D, and below 60 is an F.

The issue count is separate. It goes up when the performance score is under 90, when the page is not served over HTTPS, when the viewport or tap target checks fail, when LCP is over 2.5 seconds, and when FCP is over 1.8 seconds.

The letter itself is not something Google reads. LCP, CLS and INP are Google’s Core Web Vitals and are used as a ranking signal, so it is the underlying timings, not the grade, that carry into search.

The fixes that usually come up

Recommendations come from the Lighthouse audits your page actually failed, so they name real problems rather than giving generic advice. When the performance score is under 90 the grader checks six opportunities: render-blocking CSS and JavaScript, unused CSS, offscreen images that could be lazy-loaded, images that could be served as WebP or AVIF instead of JPEG or PNG, text compression left switched off, and slow server response time. It adds an SSL recommendation if the page is not on HTTPS, and a responsive-design one if the viewport or tap target checks fail. You see the first five.

On a hotel or restaurant site we would look at image weight and render-blocking scripts first, since galleries and booking widgets are the usual suspects. That is our judgement about where to start, not something the tool measures.

Getting a result you can act on

The grader analyses one URL per run. Test the pages that carry the bookings, not only the homepage: a room detail page, a menu page or a reservation page each need their own run.

Treat the score as a lab measurement of a single page on a simulated mobile connection, not a verdict on the whole site. It is most useful for finding what is broken and for checking whether a change worked, so run it before and after you make one.