mellowmushroom.com website review

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

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

Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

33 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Hotjar and Google CDN and others), adding 1.4 MB and 949 ms of main-thread time.

Google Tag Manager costs a phone 325 ms of main-thread work and 547 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.

Google CDN costs a phone 243 ms of main-thread work and 742 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.

Hotjar costs a phone 278 ms of main-thread work and 65 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.

Polyfills for old browsers add 50 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

6 files are served with short cache lifetimes, so returning visitors download them again (26 KiB).

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

For real visitors the layout shifts by 0.47 (75th percentile). Good is under 0.1.

Your largest element takes 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s.

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

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

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

Real visitors wait 213 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

2 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-31, real Chrome visitors' tap response (inp) went from 220 ms to 236 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 13.0 MB in 184 requests on a phone: images 9.9 MB (116), scripts 2.4 MB (32) and other files 448 KiB (25). Under 2 MB keeps phones on slow connections fast.

filters:format(webp):quality(90) weighs 596 KiB. On a phone connection a single image that size takes seconds.

12 images are downloaded at several times the size a phone draws them, for example 353c82a3736a4256aec295ede7fab547.png at 800 px wide, shown at 162 px. Resized copies would save about 802 KiB.

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

Interactive controls must not be nested: 107 elements on the page fail this check, rated serious by axe-core.

2 elements have a tabindex above 0, which scrambles the keyboard order.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

Alternative text of images should not be repeated as text: 15 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 11 pages on mellowmushroom.com and 6 external pages.

A phone browser shows 817 words, but the HTML your server sends has only 53. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

/ and https://www.mellowmushroom.com/locations all use the title “Mellow Mushroom | The Best Stone Baked Pizza”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.mellowmushroom.com/order, https://www.mellowmushroom.com/shroomroom and https://www.mellowmushroom.com/privacy-policy use the same meta description. A description written for each page earns more clicks.

https://www.mellowmushroom.com/order, https://www.mellowmushroom.com/locations, https://www.mellowmushroom.com/beverages and https://www.mellowmushroom.com/catering have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.mellowmushroom.com/order, https://www.mellowmushroom.com/careers, https://www.mellowmushroom.com/locations, https://www.mellowmushroom.com/food-philosophy, https://www.mellowmushroom.com/beverages and https://www.mellowmushroom.com/catering and 2 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 9 pages linked from your homepage and read each the way a search engine does.

113 of 260 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 error was logged to the browser console while the page loaded, for example “uuidv4() is deprecated. Use v4() from the uuid module instead.”.

Large scripts ship without source maps.

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

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

There is no form on the homepage, so every lead has to click through to another page first.

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

The homepage carries about 817 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Hotjar (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

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

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