Website review, no card needed

mountainmikespizza.com logo

mountainmikespizza.com website review

Visit site (opens in a new tab)Reviewed 20 November 202632 issues · 82 checks

This review found 32 issues worth fixing on mountainmikespizza.com, 13 of them high impact, across 82 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.8 s1.5 sMay 30Nov 141.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.6 s
Nov 7, 20261.6 s
Nov 14, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
150 ms80 msMay 30Nov 1495 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026142 ms
Jun 6, 2026132 ms
Jun 13, 2026120 ms
Jun 20, 2026104 ms
Jun 27, 202695 ms
Jul 4, 202694 ms
Jul 11, 202694 ms
Jul 18, 202694 ms
Jul 25, 202694 ms
Aug 1, 202694 ms
Aug 8, 202694 ms
Aug 15, 202693 ms
Aug 22, 202693 ms
Aug 29, 202692 ms
Sep 5, 202692 ms
Sep 12, 202692 ms
Sep 19, 202691 ms
Sep 26, 202689 ms
Oct 3, 202688 ms
Oct 10, 202688 ms
Oct 17, 202688 ms
Oct 24, 202688 ms
Oct 31, 202690 ms
Nov 7, 202692 ms
Nov 14, 202695 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of mountainmikespizza.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mountainmikespizza.com at 0.4 s0.4 s
  2. mountainmikespizza.com at 0.9 s0.9 s
  3. mountainmikespizza.com at 1.3 s1.3 s
  4. mountainmikespizza.com at 1.7 s1.7 s
  5. mountainmikespizza.com at 2.2 s2.2 s
  6. mountainmikespizza.com at 2.6 s2.6 s
  7. mountainmikespizza.com at 3.0 s3.0 s
  8. mountainmikespizza.com at 3.5 s3.5 s

Speed

12 to fix40
  • Improve image delivery

    8.3 s · 2.7 MB

    13 images could be 2.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.3 s faster on a phone.

  • Reduce unused JavaScript

    3.8 s · 533 KiB

    About 533 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.

  • Use efficient cache lifetimes

    1.6 s · 550 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 40

    40/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (px-cloud.net, Google Tag Manager and punchh.com and others), adding 1.6 MB and 1.6 s of main-thread time.

  • px-cloud.net adds 663 ms

    663 ms

    px-cloud.net costs a phone 663 ms of main-thread work and 212 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 Tag Manager adds 407 ms

    407 ms

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

  • Main-thread work: 3.5 s

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

  • 15 long tasks on the main thread

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

  • 1,562 HTML elements

    The page has 1,562 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Attentive adds 55 ms

    55 ms

    Attentive costs a phone 55 ms of main-thread work and 386 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.

  • Reduce unused CSS

    180 ms · 77 KiB

    About 77 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 180 ms faster on a phone.

  • Legacy JavaScript

    150 ms · 7 KiB

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

  • Minify JavaScript

    13 KiB

    13 KiB could be saved by minifying JavaScript.

  • Minify CSS

    10 KiB

    10 KiB could be saved by minifying CSS.

  • Chained critical requests

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

  • Forced reflow

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

1 checks passed
  • Server response: 6 ms

    6 ms

    Your server sent the HTML in 6 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • First Contentful Paint: 7.8 s

    7.8 s

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

  • Largest Contentful Paint: 29.2 s

    29.2 s

    Your largest element takes 29.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Mountain Mike's Pizza Previous Slide DOWNLOAD OUR APP ENTER…”.

  • Time to Interactive: 29.3 s

    29.3 s

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

  • Speed Index: 11.1 s

    11.1 s

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

  • Total Blocking Time: 634 ms

    634 ms

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

  • Largest content (LCP) held steady for real visitors

    -7%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.6 s

    1.6 s

    Real visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 83 ms

    83 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.3 s

    1.3 s

    Real visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 556 ms

    556 ms

    Real visitors wait 556 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 32% faster for real visitors

    -32%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 142 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 8.9 MB in 158 requests

    8.9 MB

    Your homepage downloads 8.9 MB in 158 requests on a phone: images 3.4 MB (22), other files 3.0 MB (51) and scripts 1.5 MB (47). Under 2 MB keeps phones on slow connections fast.

  • 7 images in older formats

    7 images (1.5 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 2.5 g of CO₂ per visit

    2.53 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

Google 100100
2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 17 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 17 WCAG 2.2 A/AA and best-practice rules on the phone render: 17 passed and 0 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8374
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (21 characters)

    Your title is only 21 characters: “Mountain Mike's Pizza”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

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

  • No XML sitemap

    No XML sitemap at https://www.mountainmikespizza.com/sitemap_index.xml, so Google discovers your pages only by following links.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

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

  • 35 internal links, 19 external

    The homepage links to 35 pages on mountainmikespizza.com and 19 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Mountain Mike's Pizza”.

  • Canonical URL set

    The canonical URL is https://www.mountainmikespizza.com/.

  • Structured data in place

    Structured data found: BreadcrumbList.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (516 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.mountainmikespizza.com/llms.txt (1 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 15 pages without a meta description

    https://www.mountainmikespizza.com/menu, https://www.mountainmikespizza.com/locations, https://www.mountainmikespizza.com/rewards, https://www.mountainmikespizza.com/fundraising, https://www.mountainmikespizza.com/catering and https://www.mountainmikespizza.com/group-events and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 3583
  • 65 small tap targets

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

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • No social proof

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

  • No direct contact details

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

  • No form on the homepage

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

  • No risk reducer

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

  • About 566 words of copy

    The homepage carries about 566 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “START ORDER FOR MY MOUNTAIN MIKE'S” and “ORDER NOW”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “Start Order for My Mountain Mike's”, “Order Now” and “Order Now!”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

  • 4 trackers load before any consent

    4

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

  • 19 cookies set on arrival

    19

    Opening the homepage sets 19 cookies, 2 of them by other companies (measured from a US location before any click).

  • 36 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at mountainmikespizza.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on mountainmikespizza.com, including 17 speed issues, 5 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25