Website review, no card needed
eatatjacks.com website review
Visit site (opens in a new tab)Reviewed 1 November 202641 issues · 85 checks
This review found 41 issues worth fixing on eatatjacks.com, 17 of them high impact, across 85 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
78C- #62,091 of 123,862 reviewed websitesbeats 44%
- #40,533 of 69,698 online storesbeats 36%
- #937 of 2,896 WooCommerce storesbeats 62%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.2 s |
| May 16, 2026 | 1.2 s |
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 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.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 112 ms |
| May 16, 2026 | 112 ms |
| May 23, 2026 | 113 ms |
| May 30, 2026 | 117 ms |
| Jun 6, 2026 | 127 ms |
| Jun 13, 2026 | 137 ms |
| Jun 20, 2026 | 144 ms |
| Jun 27, 2026 | 150 ms |
| Jul 4, 2026 | 150 ms |
| Jul 11, 2026 | 152 ms |
| Jul 18, 2026 | 152 ms |
| Jul 25, 2026 | 154 ms |
| Aug 1, 2026 | 158 ms |
| Aug 8, 2026 | 164 ms |
| Aug 15, 2026 | 170 ms |
| Aug 22, 2026 | 175 ms |
| Aug 29, 2026 | 176 ms |
| Sep 5, 2026 | 175 ms |
| Sep 12, 2026 | 177 ms |
| Sep 19, 2026 | 177 ms |
| Sep 26, 2026 | 178 ms |
| Oct 3, 2026 | 178 ms |
| Oct 10, 2026 | 178 ms |
| Oct 17, 2026 | 177 ms |
| Oct 24, 2026 | 177 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
5.0 s · 927 KiBAbout 927 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.0 s faster on a phone.
Use efficient cache lifetimes
1.6 s · 391 KiB20 files are served with short cache lifetimes, so returning visitors download them again (391 KiB).
Render-blocking requests
1.5 s32 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Google Tag Manager adds 1.1 s
1.1 sGoogle Tag Manager costs a phone 1.1 s of main-thread work and 1.2 MB 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: 40
40/100Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
750 ms · 4.0 MB19 images could be 4.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 1.9 MB and 1.6 s of main-thread time.
Main-thread work: 3.5 s
A phone's processor spends 3.5 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
300 ms · 32 KiBPolyfills for old browsers add 32 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 259 ms. During a long task the page ignores taps.
Reduce unused CSS
60 ms · 12 KiBAbout 12 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 60 ms faster on a phone.
Minify JavaScript
60 ms · 5 KiB5 KiB could be saved by minifying JavaScript.
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: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 26.9 s
26.9 sYour largest element takes 26.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “nugget meal deal mobile”.
Time to Interactive: 30.3 s
30.3 sThe page becomes fully interactive after 30.3 s. Good is under 3.8 s.
Speed Index: 11.8 s
11.8 sVisually, the page fills in at 11.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.4 s
4.4 sThe first text or image appears after 4.4 s on a phone. Good is under 1.8 s.
Total Blocking Time: 704 ms
704 msScripts block taps and scrolling for 704 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 58% slower for real visitors
+58%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 112 ms to 177 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 185 ms
185 msReal visitors wait 185 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 721 ms
721 msReal visitors wait 721 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 9.1 MB in 243 requests
9.1 MBYour homepage downloads 9.1 MB in 243 requests on a phone: images 6.2 MB (62), scripts 2.2 MB (65) and fonts 427 KiB (6). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
Jacks-Milkshakes-scaled.png weighs 804 KiB. On a phone connection a single image that size takes seconds.
An image on the first screen is lazy-loaded
nugget-meal-deal-mobile-scaled-1-600x715.jpg 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).
4 images in older formats
4 images (738 KiB) 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.6 g of CO₂ per visit
2.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.58 g of CO₂e: 309.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Images must have alternative text (3 elements)
Images must have alternative text: 3 elements on the page fail this check, rated critical by axe-core.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
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 (3 elements)
ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 3 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.
Meta description is long (170 characters)
Your meta description is 170 characters; Google truncates after about 160, so the end of your pitch is cut.
91 internal links, 33 external
The homepage links to 91 pages on eatatjacks.com and 33 external pages.
6 checks passed
Title: 32 characters
Your title is a healthy 32 characters: “HOME - Jack's Family Restaurants”.
Canonical URL set
The canonical URL is https://www.eatatjacks.com/.
Structured data in place
Structured data found: 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.eatatjacks.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.eatatjacks.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 (658 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share 2 titles
https://www.eatatjacks.com/pages/our-story and https://www.eatatjacks.com/our-story all use the title “Our Story - Jack's Family Restaurants”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.eatatjacks.com/privacy-policy has no meta description, so Google writes the search snippet from whatever text it finds.
4 pages share a meta description
https://www.eatatjacks.com/pages/our-story and https://www.eatatjacks.com/our-story use the same meta description. A description written for each page earns more clicks.
4 links to non-canonical URLs
Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.eatatjacks.com/career-opportunities, whose canonical is https://www.eatatjacks.com/pages/career-opportunities. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 pages without an H1
https://www.eatatjacks.com/pages/our-story, https://www.eatatjacks.com/pages/career-opportunities, https://www.eatatjacks.com/product-category/featured-items, https://www.eatatjacks.com/product-category/breakfast, https://www.eatatjacks.com/product-category/sandwiches and https://www.eatatjacks.com/product-category/chicken and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 36 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
4 third-party cookies
4 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 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
38 of 40 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.
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 464 words of copy
The homepage carries about 464 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “ORDER NOW”.
16 calls to action
The homepage has 16 calls to action, for example “Order Now”, “ORDER NOW” and “APPLY HERE”.
1 short form
A short form (3 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Hotjar and TikTok Pixel.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 5 mores (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.
37 cookies set on arrival
37Opening the homepage sets 37 cookies (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.
60 other companies contacted
Loading the homepage contacts 60 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 eatatjacks.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
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
- Hosting
- WP Engine
Company
- Founded
- 1960
- Headquarters
- Birmingham
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on eatatjacks.com, including 17 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.