Website review, no card needed
giordanos.com website review
Visit site (opens in a new tab)Reviewed 18 November 202648 issues · 84 checks
This review found 48 issues worth fixing on giordanos.com, 19 of them high impact, across 84 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
72CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.5 s |
| Nov 14, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 154 ms |
| Jun 6, 2026 | 154 ms |
| Jun 13, 2026 | 154 ms |
| Jun 20, 2026 | 153 ms |
| Jun 27, 2026 | 154 ms |
| Jul 4, 2026 | 154 ms |
| Jul 11, 2026 | 158 ms |
| Jul 18, 2026 | 162 ms |
| Jul 25, 2026 | 164 ms |
| Aug 1, 2026 | 170 ms |
| Aug 8, 2026 | 174 ms |
| Aug 15, 2026 | 179 ms |
| Aug 22, 2026 | 184 ms |
| Aug 29, 2026 | 187 ms |
| Sep 5, 2026 | 187 ms |
| Sep 12, 2026 | 187 ms |
| Sep 19, 2026 | 187 ms |
| Sep 26, 2026 | 191 ms |
| Oct 3, 2026 | 197 ms |
| Oct 10, 2026 | 203 ms |
| Oct 17, 2026 | 206 ms |
| Oct 24, 2026 | 209 ms |
| Oct 31, 2026 | 208 ms |
| Nov 7, 2026 | 206 ms |
| Nov 14, 2026 | 203 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
Speed
Improve image delivery
7.3 s · 6.9 MB31 images could be 6.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.3 s faster on a phone.
Reduce unused JavaScript
1.9 s · 595 KiBAbout 595 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Render-blocking requests
1.1 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Google Tag Manager adds 1.0 s
1.0 sGoogle Tag Manager costs a phone 1.0 s of main-thread work and 692 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 18.5 MB and 2.0 s of main-thread time.
Use efficient cache lifetimes
300 ms · 2.0 MB64 files are served with short cache lifetimes, so returning visitors download them again (2.0 MB).
juicer.io adds 112 ms
112 msjuicer.io costs a phone 112 ms of main-thread work and 17.3 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.
Facebook adds 543 ms
543 msFacebook costs a phone 543 ms of main-thread work and 305 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
450 ms · 67 KiBAbout 67 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 373 ms. During a long task the page ignores taps.
TikTok adds 303 ms
303 msTikTok costs a phone 303 ms of main-thread work and 162 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.
Legacy JavaScript
150 ms · 26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Largest Contentful Paint: 46.6 s
46.6 sYour largest element takes 46.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 15.8 s
15.8 sVisually, the page fills in at 15.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 48.7 s
48.7 sThe page becomes fully interactive after 48.7 s. Good is under 3.8 s.
Total Blocking Time: 897 ms
897 msScripts block taps and scrolling for 897 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 212 ms
212 msReal visitors wait 212 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 33% slower for real visitors
+33%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 154 ms to 203 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 805 ms
805 msReal visitors wait 805 ms for your server to start answering (75th percentile). Good is under 800 ms.
25 images without width and height
25 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
4 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 27.7 MB in 139 requests
27.7 MBYour homepage downloads 27.7 MB in 139 requests on a phone: images 24.4 MB (79), media 1.5 MB (1) and scripts 1.3 MB (23). Under 2 MB keeps phones on slow connections fast.
12 images over 500 KB
12 images weigh 15.3 MB together. On a phone connection a single image that size takes seconds.
24 images far larger than shown
12.4 MB24 images are downloaded at several times the size a phone draws them, for example 32005574 at 3,072 px wide, shown at 306 px. Resized copies would save about 12.4 MB.
38 images in older formats
38 images (22.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.
25 images below the first screen load straight away
25 images further down the page (17.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
An image on the first screen is lazy-loaded
Giordanos-Logo-Chicago-Style-Pizza-Lockup-768x294.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 7.8 g of CO₂ per visit
7.84 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.84 g of CO₂e: 941.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Orphan list items
Some list items are not inside a list.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 27 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
33 internal links, 22 external
The homepage links to 33 pages on giordanos.com and 22 external pages.
7 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “Serving Chicago-style deep dish stuffed pizza since 1974. Explore our menu and place an online order for delivery or ca…”.
Title: 52 characters
Your title is a healthy 52 characters: “Authentic Chicago Deep Dish Pizza | Giordano's Pizza”.
Canonical URL set
The canonical URL is https://giordanos.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://giordanos.com/sitemap_index.xml.
AI search readiness
Some text only appears after JavaScript runs
33%The HTML your server sends has 662 of the 1,984 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://giordanos.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.
1 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.
Other pages
2 pages share a title
https://giordanos.com/private-events and https://giordanos.com/event-space all use the title “Private Events - Giordanos”. Search engines can't tell which page to show for a search, so each competes with the others.
7 pages without a meta description
https://giordanos.com/locations, https://giordanos.com/private-events, https://giordanos.com/rewards, https://giordanos.com/press, https://giordanos.com/fundraisers-donations and https://giordanos.com/lunch-special and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://giordanos.com/event-space, whose canonical is https://giordanos.com/private-events. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://giordanos.com/locations and https://giordanos.com/lunch-special have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://giordanos.com/locations and https://giordanos.com/talk-to-us 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5140138&Ver=2&mid=02ba03ae-33ac-46c3-adb8-72452e09ed04&bo=1&sid=5e4b1230e2f411f18af3996269c75932&vid=5e4b4270e2f411f18e08f1e94e64fb81&vids=1&msclkid=N&pi=918639831&lg=.
2 small tap targets
2 of 6 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
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 1,984 words of copy
The homepage carries about 1,984 words of visible text.
2 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Join our Team”, “Join Club Gio” and “Talk To Us”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (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.
17 cookies set on arrival
17Opening the homepage sets 17 cookies, 1 of them by other companies (measured from a US location before any click).
No consent tool detected
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.
17 other companies contacted
Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 giordanos.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- HAProxy Technologies, Inc.
Company
- Founded
- 1974
- Headquarters
- Chicago
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on giordanos.com, including 24 speed issues, 2 SEO issues and 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.