uspizza.com website review

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

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

About 1.6 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 8.6 s faster on a phone.

8 images could be 773 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

About 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

952 KiB could be saved by minifying JavaScript.

193 KiB could be saved by minifying CSS.

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

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

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

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

1 third-party service load with your homepage (Google Fonts), adding 42 KiB and 0 ms of main-thread time.

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

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

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

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

The layout shifts by 0.126 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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 6.6 MB in 38 requests on a phone: scripts 2.7 MB (12), images 1.9 MB (16) and stylesheets 1.7 MB (7). Under 2 MB keeps phones on slow connections fast.

US-Pizza-Rider-Delivery-New.gif weighs 632 KiB. On a phone connection a single image that size takes seconds.

8 images (1.1 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.

7 images further down the page (1.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

3 tap targets are too small or too close together to hit reliably with a finger.

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

Headings skip levels (h1 → h6), which makes the page harder to scan with a screen reader.

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

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

There are 3 <h1> headlines (“Serving The Best American-Style Pizza For Over 24…”, “Bringing Pizza Goodness to the World!” and “FOLLOW US ONLINE”). One clear main headline is easier for people and search engines.

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 12 pages on uspizza.com and 6 external pages.

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.

There is no /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.

/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and /home all use the title “US PIZZA – Official International Site of US Pizza”. Search engines can't tell which page to show for a search, so each competes with the others.

/home, /our-story, /franchising, /corporate-membership, /contact-us and /locations have no meta description, so Google writes the search snippet from whatever text it finds.

/corporate-membership and /locations 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.

/home took over 3 s to send its HTML from our server.

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

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

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 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 150 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.

Opening the homepage sets 1 cookie (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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.