jfrestaurants.com website review

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.7 s.

8 third-party services load with your homepage (getbento.com, Google CDN and Klaviyo and others), adding 4.1 MB and 1.3 s of main-thread time.

8 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).

Your mobile performance score is 63 (desktop: 86). Pages that score under 90 lose visitors before the first paint.

getbento.com costs a phone 699 ms of main-thread work and 2.7 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 810 KiB of JavaScript is downloaded but never used on this page.

Google CDN costs a phone 414 ms of main-thread work and 733 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

A phone's processor spends 2.8 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

11 long tasks block the main thread while loading, the longest for 147 ms. During a long task the page ignores taps.

9 images could be 83 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 79 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 57 KiB JavaScript that modern phones do not need.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

The page becomes fully interactive after 23.4 s. Good is under 3.8 s.

Visually, the page fills in at 9.0 s (Speed Index). Good is under 3.4 s.

The first text or image appears after 3.7 s on a phone. Good is under 1.8 s.

Your largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “John Fraser Restaurants Home”.

Scripts block taps and scrolling for 445 ms in total while the page loads. Good is under 200 ms.

9 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.3 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.4 MB in 83 requests on a phone: scripts 2.7 MB (36), images 875 KiB (21) and fonts 434 KiB (8). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 1.26 g of CO₂e: 151.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

8 visible links have no text or label, so screen readers cannot say where they go.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Your title is only 14 characters: “JF Restaurants”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“Home” and “‎”). One clear main headline is easier for people and search engines.

The homepage links to 47 pages on jfrestaurants.com and 16 external pages.

There is no https://www.jfrestaurants.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.jfrestaurants.com/our-story, https://www.jfrestaurants.com/location/north-fork-table-inn, https://www.jfrestaurants.com/the-times-square-edition, https://www.jfrestaurants.com/the-wall-street-hotel, https://www.jfrestaurants.com/location/obvio-nyc and https://www.jfrestaurants.com/location/casa-cruz and 8 others use the same meta description. A description written for each page earns more clicks.

https://www.jfrestaurants.com/the-times-square-edition, https://www.jfrestaurants.com/the-wall-street-hotel, https://www.jfrestaurants.com/the-tampa-edition and https://www.jfrestaurants.com/winthrop-center-boston have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 21 found) and read each the way a search engine does.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 119 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Klaviyo (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 11 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.