Website review, no card needed
fallonandbyrne.com website review
Visit site (opens in a new tab)Reviewed 24 October 202640 issues · 88 checks
This review found 40 issues worth fixing on fallonandbyrne.com, 17 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. 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
69D- #106,469 of 124,214 reviewed websitesbeats 12%
- #64,029 of 69,818 online storesbeats 7%
- #2,354 of 2,907 WooCommerce storesbeats 16%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.6 s |
| May 9, 2026 | 1.6 s |
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 633 ms |
| May 9, 2026 | 617 ms |
| May 16, 2026 | 595 ms |
| May 23, 2026 | 616 ms |
| May 30, 2026 | 641 ms |
| Jun 6, 2026 | 659 ms |
| Jun 13, 2026 | 664 ms |
| Jun 20, 2026 | 646 ms |
| Jun 27, 2026 | 651 ms |
| Jul 4, 2026 | 656 ms |
| Jul 11, 2026 | 655 ms |
| Jul 18, 2026 | 655 ms |
| Jul 25, 2026 | 664 ms |
| Aug 1, 2026 | 701 ms |
| Aug 8, 2026 | 744 ms |
| Aug 15, 2026 | 737 ms |
| Aug 22, 2026 | 749 ms |
| Aug 29, 2026 | 746 ms |
| Sep 5, 2026 | 723 ms |
| Sep 12, 2026 | 720 ms |
| Sep 19, 2026 | 624 ms |
| Sep 26, 2026 | 483 ms |
| Oct 3, 2026 | 351 ms |
| Oct 10, 2026 | 274 ms |
| Oct 17, 2026 | 265 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
How it loaded on a phone
0.9 s
1.8 s
2.7 s
3.6 s
4.4 s
5.3 s
6.2 s
7.1 s
Speed
Reduce unused JavaScript
3.1 s · 756 KiBAbout 756 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.
Render-blocking requests
3.8 s73 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.8 s.
Use efficient cache lifetimes
2.5 s · 584 KiB188 files are served with short cache lifetimes, so returning visitors download them again (584 KiB).
Mobile performance score: 31
31/100Your mobile performance score is 31 (desktop: 31). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.0 s
A phone's processor spends 7.0 s on main-thread work while loading, 5.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 2.4 s. During a long task the page ignores taps.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 2.0 MB and 872 ms of main-thread time.
Reduce unused CSS
600 ms · 154 KiBAbout 154 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Google CDN adds 252 ms
252 msGoogle CDN costs a phone 252 ms of main-thread work and 734 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 262 ms
262 msGoogle Tag Manager costs a phone 262 ms of main-thread work and 371 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.
2,738 HTML elements
The page has 2,738 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 83 ms
83 msKlaviyo costs a phone 83 ms of main-thread work and 328 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.
Improve image delivery
200 ms · 36 KiB2 images could be 36 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Legacy JavaScript
150 ms · 61 KiBPolyfills for old browsers add 61 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify CSS
7 KiB7 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: 37 ms
37 msYour server sent the HTML in 37 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: 17.7 s
17.7 sYour largest element takes 17.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “christmas home banner”.
Time to Interactive: 22.1 s
22.1 sThe page becomes fully interactive after 22.1 s. Good is under 3.8 s.
Total Blocking Time: 2.8 s
2.8 sScripts block taps and scrolling for 2.8 s in total while the page loads. Good is under 200 ms.
Speed Index: 11.3 s
11.3 sVisually, the page fills in at 11.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.8 s
3.8 sReal visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 435 ms
435 msReal visitors wait 435 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 82% slower for real visitors
+82%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.6 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.9 s
2.9 sReal visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
3 checks passed
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Tap response (INP) got 57% faster for real visitors
-57%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 633 ms to 265 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.006
0.006The layout barely moves while loading (CLS 0.006, good is under 0.1).
Images and page weight
Page weight: 3.4 MB in 252 requests
3.4 MBYour homepage downloads 3.4 MB in 252 requests on a phone: scripts 2.4 MB (142), other files 373 KiB (15) and stylesheets 295 KiB (67). Under 2 MB keeps phones on slow connections fast.
About 1.0 g of CO₂ per visit
0.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.97 g of CO₂e: 116.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Orphan list items
Some list items are not inside a list.
11 images without alt text
11 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
173 internal links, 15 external
The homepage links to 173 pages on fallonandbyrne.com and 15 external pages.
8 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Experience gourmet food and exceptional dining at Fallon & Byrne. Explore our exquisite menus, fine wines, and artisana…”.
One H1 headline
Your main headline reads: “The Ultimate Christmas Gifts for Food Lovers”.
Title: 49 characters
Your title is a healthy 49 characters: “Gourmet Food, Fine Dining, and Artisanal Products”.
Canonical URL set
The canonical URL is https://www.fallonandbyrne.com/.
Structured data in place
Structured data found: BreadcrumbList, 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://www.fallonandbyrne.com/sitemap_index.xml.
AI search readiness
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.
No llms.txt
There is no https://www.fallonandbyrne.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.
2 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 (803 words), so crawlers that don't run JavaScript still read it.
Other pages
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.fallonandbyrne.com/hampers-gifts, whose canonical is https://www.fallonandbyrne.com/hampers-gifts-cards. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 88 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
6 broken images
6 images failed to load on a phone, for example https://www.fallonandbyrne.com/.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
90 of 97 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
About 980 words of copy
The homepage carries about 980 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book yours here.” and “Book a Table”.
12 calls to action
The homepage has 12 calls to action, for example “Book yours here.”, “Rosé & Skin Contact Wines” and “Contact”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.
9 cookies set on arrival
9Opening the homepage sets 9 cookies (measured from a US location before any click).
21 other companies contacted
Loading the homepage contacts 21 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 fallonandbyrne.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
- React
- E-commerce
- WooCommerce
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on fallonandbyrne.com, including 23 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.