Website review, no card needed
acmestores.com website review
Visit site (opens in a new tab)Reviewed 7 November 202650 issues · 90 checks
This review found 50 issues worth fixing on acmestores.com, 18 of them high impact, across 90 checks. The most urgent: use efficient cache lifetimes. 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
64DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.2 s |
| May 23, 2026 | 3.2 s |
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.3 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 3.5 s |
| Aug 1, 2026 | 3.5 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 3.6 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 3.5 s |
| Oct 24, 2026 | 3.5 s |
| Oct 31, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 153 ms |
| May 23, 2026 | 154 ms |
| May 30, 2026 | 155 ms |
| Jun 6, 2026 | 158 ms |
| Jun 13, 2026 | 159 ms |
| Jun 20, 2026 | 158 ms |
| Jun 27, 2026 | 162 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 161 ms |
| Jul 18, 2026 | 162 ms |
| Jul 25, 2026 | 161 ms |
| Aug 1, 2026 | 161 ms |
| Aug 8, 2026 | 167 ms |
| Aug 15, 2026 | 178 ms |
| Aug 22, 2026 | 187 ms |
| Aug 29, 2026 | 196 ms |
| Sep 5, 2026 | 204 ms |
| Sep 12, 2026 | 211 ms |
| Sep 19, 2026 | 213 ms |
| Sep 26, 2026 | 221 ms |
| Oct 3, 2026 | 223 ms |
| Oct 10, 2026 | 229 ms |
| Oct 17, 2026 | 241 ms |
| Oct 24, 2026 | 246 ms |
| Oct 31, 2026 | 251 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
1.5 s
3.0 s
4.5 s
6.0 s
7.5 s
8.9 s
10.4 s
11.9 s
Speed
Use efficient cache lifetimes
5.2 s · 6.5 MB499 files are served with short cache lifetimes, so returning visitors download them again (6.5 MB).
Improve image delivery
3.1 s · 2.7 MB199 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 3.1 s faster on a phone.
Main-thread work: 13.6 s
A phone's processor spends 13.6 s on main-thread work while loading, 10.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.3 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 22
22/100Your mobile performance score is 22. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
9,535 HTML elements
The page has 9,535 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 8.2 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, Facebook and brandcdn.com and others), adding 1.3 MB and 1.8 s of main-thread time.
Google Tag Manager adds 779 ms
779 msGoogle Tag Manager costs a phone 779 ms of main-thread work and 427 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.
Facebook adds 548 ms
548 msFacebook costs a phone 548 ms of main-thread work and 395 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 JavaScript
297 KiBAbout 297 KiB of JavaScript is downloaded but never used on this page.
brandcdn.com adds 268 ms
268 msbrandcdn.com costs a phone 268 ms of main-thread work and 14 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.
Adobe TypeKit adds 22 ms
22 msAdobe TypeKit costs a phone 22 ms of main-thread work and 354 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.
Minify JavaScript
110 ms · 90 KiB90 KiB could be saved by minifying JavaScript.
Reduce unused CSS
89 KiBAbout 89 KiB of CSS is downloaded but never applied on this page.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
28 KiB28 KiB could be saved by minifying CSS.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
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: 77 ms
77 msYour server sent the HTML in 77 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.
Real-user INP: 2.2 s
2.2 sReal visitors wait 2.2 s for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 1.9 s
1.9 sReal visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 13.1 s
13.1 sYour largest element takes 13.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 5.4 s
5.4 sScripts block taps and scrolling for 5.4 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 30.6 s
30.6 sThe page becomes fully interactive after 30.6 s. Good is under 3.8 s.
Speed Index: 9.7 s
9.7 sVisually, the page fills in at 9.7 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 62% slower for real visitors
+62%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 153 ms to 251 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
143 images without width and height
143 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.229
0.229The layout shifts by 0.229 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.2 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Images and page weight
Page weight: 8.1 MB in 620 requests
8.1 MBYour homepage downloads 8.1 MB in 620 requests on a phone: images 5.8 MB (467), scripts 1.2 MB (50) and fonts 782 KiB (21). Under 2 MB keeps phones on slow connections fast.
8 images far larger than shown
1.0 MB8 images are downloaded at several times the size a phone draws them, for example 4916 at 2,000 px wide, shown at 238 px. Resized copies would save about 1.0 MB.
10 images in older formats
10 images (1.4 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.
5 images below the first screen load straight away
5 images further down the page (767 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.3 g of CO₂ per visit
2.30 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.30 g of CO₂e: 275.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
466 images without alt text
466 images have no alt text, which hurts accessibility and image search.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (1,803 elements)
All page content should be contained by landmarks: 1,803 elements on the page fail this check, rated moderate by axe-core.
458 links without text
458 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h6, h1 → h6 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
6 H1 headlines
There are 6 <h1> headlines (“Shop Your Favorites!”, “My Shopping List Dropdown” and “Manage Shopping List”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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.acmestores.com/sitemap.xml, so Google discovers your pages only by following links.
16 links crawlers can't follow
16 links have no real href, so search engines can't follow them.
No robots.txt
There is no robots.txt at acmestores.com/robots.txt, the first file search crawlers ask for.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
971 internal links, 14 external
The homepage links to 971 pages on acmestores.com and 14 external pages.
2 checks passed
Meta description: 74 characters
Your meta description is 74 characters: “Grocery Pick Up & Delivery, Weekly Ad, Digital Coupons, Recipes, and more!”.
Title: 63 characters
Your title is a healthy 63 characters: “Acme Fresh Market - Acme Fresh Market: Local Ohio Grocery Store”.
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.acmestores.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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (7,920 words), so crawlers that don't run JavaScript still read it.
Other pages
11 pages without a meta description
https://www.acmestores.com/products, https://www.acmestores.com/weddingcakes, https://www.acmestores.com/recipes, https://www.acmestores.com/page/127, https://www.acmestores.com/page/184 and https://www.acmestores.com/page/130 and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages slow to respond
https://www.acmestores.com/shop, https://www.acmestores.com/products, https://www.acmestores.com/weddingcakes and https://www.acmestores.com/recipes took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 187 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.
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 14 pages that loaded have a <title>.
Best practices
11 third-party cookies
11 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'offsetWidth')”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
614 of 639 tappable elements near the top are at least 24 px.
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 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 6,380 words of copy
The homepage carries about 6,380 words of visible text.
4 checks passed
10 calls to action
The homepage has 10 calls to action, for example “Reserve a time for your order.”, “SHOP” and “Shop Pickup”.
5 short forms
5 short forms (2 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and The Trade Desk (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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
35 other companies contacted
Loading the homepage contacts 35 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 acmestores.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- AWS
Company
- Founded
- 1891
- Headquarters
- Akron
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 50 issues on acmestores.com, including 26 speed issues, 8 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.