Website review, no card needed
acmecorp.com website review
Visit site (opens in a new tab)Reviewed 18 October 202640 issues · 84 checks
This review found 40 issues worth fixing on acmecorp.com, 14 of them high impact, across 84 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
78C- #59,264 of 117,059 reviewed websitesbeats 44%
- #39,109 of 66,858 online storesbeats 36%
- #173 of 711 Magento storesbeats 71%
Closest competitors among Magento stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 1.9 s |
| May 2, 2026 | 1.8 s |
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 79 ms |
| May 2, 2026 | 78 ms |
| May 9, 2026 | 78 ms |
| May 16, 2026 | 79 ms |
| May 23, 2026 | 78 ms |
| May 30, 2026 | 78 ms |
| Jun 6, 2026 | 75 ms |
| Jun 13, 2026 | 72 ms |
| Jun 20, 2026 | 72 ms |
| Jun 27, 2026 | 71 ms |
| Jul 4, 2026 | 71 ms |
| Jul 11, 2026 | 71 ms |
| Jul 18, 2026 | 71 ms |
| Jul 25, 2026 | 70 ms |
| Aug 1, 2026 | 71 ms |
| Aug 8, 2026 | 70 ms |
| Aug 15, 2026 | 69 ms |
| Aug 22, 2026 | 69 ms |
| Aug 29, 2026 | 66 ms |
| Sep 5, 2026 | 68 ms |
| Sep 12, 2026 | 67 ms |
| Sep 19, 2026 | 65 ms |
| Sep 26, 2026 | 69 ms |
| Oct 3, 2026 | 68 ms |
| Oct 10, 2026 | 71 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
Use efficient cache lifetimes
5.3 s · 10.2 MB311 files are served with short cache lifetimes, so returning visitors download them again (10.2 MB).
Improve image delivery
10.6 s · 4.4 MB35 images could be 4.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 10.6 s faster on a phone.
Main-thread work: 6.8 s
A phone's processor spends 6.8 s on main-thread work while loading, 3.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
7 third-party services on the page
7 third-party services load with your homepage (Google CDN, Clarity and Google Tag Manager and others), adding 1.5 MB and 1.1 s of main-thread time.
Reduce unused CSS
990 ms · 212 KiBAbout 212 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 990 ms faster on a phone.
Mobile performance score: 51
51/100Your mobile performance score is 51 (desktop: 52). Pages that score under 90 lose visitors before the first paint.
Google CDN adds 657 ms
657 msGoogle CDN costs a phone 657 ms of main-thread work and 1.1 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.
Reduce unused JavaScript
618 KiBAbout 618 KiB of JavaScript is downloaded but never used on this page.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 192 ms. During a long task the page ignores taps.
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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 43 ms
43 msYour server sent the HTML in 43 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: 40.1 s
40.1 sYour largest element takes 40.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “2026 Fall HP”.
Speed Index: 27.8 s
27.8 sVisually, the page fills in at 27.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 89.9 s
89.9 sThe page becomes fully interactive after 89.9 s. Good is under 3.8 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 354 ms
354 msScripts block taps and scrolling for 354 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 72 ms
72 msReal visitors wait 72 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 79 ms to 71 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.072
0.072The layout barely moves while loading (CLS 0.072, good is under 0.1).
Images and page weight
Page weight: 27.6 MB in 352 requests
27.6 MBYour homepage downloads 27.6 MB in 352 requests on a phone: images 24.6 MB (54), scripts 1.8 MB (261) and other files 731 KiB (23). Under 2 MB keeps phones on slow connections fast.
12 images over 500 KB
12 images weigh 21.4 MB together. On a phone connection a single image that size takes seconds.
15 images far larger than shown
18.5 MB15 images are downloaded at several times the size a phone draws them, for example HP_virtural_showroom_banner.jpg at 4,130 px wide, shown at 390 px. Resized copies would save about 18.5 MB.
39 images in older formats
39 images (23.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.
16 images below the first screen load straight away
16 images further down the page (1.4 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
HP_virtural_showroom_banner.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).
About 7.8 g of CO₂ per visit
7.83 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.83 g of CO₂e: 939.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
30 text elements with low contrast
30 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (5 elements)
Interactive controls must not be nested: 5 elements on the page fail this check, rated serious 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.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 35 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 4 failed. 3 mores 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.
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.
7 links with vague text
7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
153 internal links, 15 external
The homepage links to 153 pages on acmecorp.com and 15 external pages.
5 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Shop Acme Furniture to fit your lifestyle. More than 5,000 brands of furniture, beds, sofa, chairs, lighting, and more.…”.
One H1 headline
Your main headline reads: “Become A Dealer”.
Title: 57 characters
Your title is a healthy 57 characters: “Acme Furniture - The best source of fine home furnishings”.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://acmecorp.com/sitemap.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://acmecorp.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 (433 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
/ and https://acmecorp.com/losangeles all use the title “Acme Furniture - The best source of fine home furnishings”. Search engines can't tell which page to show for a search, so each competes with the others.
13 pages without a meta description
https://acmecorp.com/losangeles/current-catalogs, https://acmecorp.com/losangeles/new-account, https://acmecorp.com/losangeles/catalogsearch/advanced, https://acmecorp.com/losangeles/on-sale.html, https://acmecorp.com/losangeles/on-sale/clearance-sale.html and https://acmecorp.com/losangeles/on-sale/high-demand-best-seller.html and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://acmecorp.com/losangeles/new-account has 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 110 found) and read each the way a search engine does.
4 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.
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
14 small tap targets
14 of 70 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
1 checks passed
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 307 words of copy
The homepage carries about 307 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn More” and “WHERE TO BUY”.
7 calls to action
The homepage has 7 calls to action, for example “Learn More”, “WHERE TO BUY” and “Apply Now”.
3 short forms
3 short forms (4 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 5 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Microsoft Clarity (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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
13 other companies contacted
Loading the homepage contacts 13 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 acmecorp.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2019.
Stack
- E-commerce
- Magento
- Analytics
- Microsoft Clarity
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 acmecorp.com, including 16 speed issues, 4 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.