Website review, no card needed
aceitpolish.com website review
Visit site (opens in a new tab)Reviewed 17 November 202639 issues · 75 checks
This review found 39 issues worth fixing on aceitpolish.com, 21 of them high impact, across 75 checks. The most urgent: reduce unused CSS. 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
61D- #111,858 of 115,554 reviewed websitesbeats 3%
- #65,714 of 66,525 online storesbeats 1%
- #617 of 695 Magento storesbeats 9%
Closest competitors among Magento stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.5 s
1.0 s
1.5 s
2.0 s
2.5 s
3.0 s
3.5 s
4.0 s
Speed
Reduce unused CSS
6.2 s · 1.0 MBAbout 1.0 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 6.2 s faster on a phone.
Minify JavaScript
5.9 s · 965 KiB965 KiB could be saved by minifying JavaScript.
Render-blocking requests
5.5 s19 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.5 s.
Improve image delivery
4.4 s · 834 KiB2 images could be 834 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.4 s faster on a phone.
Reduce unused JavaScript
4.5 s · 760 KiBAbout 760 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.5 s faster on a phone.
Mobile performance score: 35
35/100Your mobile performance score is 35. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Use efficient cache lifetimes
200 ms · 31 KiB1 file is served with short cache lifetimes, so returning visitors download them again (31 KiB).
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
1 long task on the main thread
1 long task block the main thread while loading, the longest for 53 ms. During a long task the page ignores taps.
Document request latency
34 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
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.
1 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 54 KiB and 0 ms of main-thread time.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 775 ms of it running JavaScript. That is comfortably low.
Server response: 46 ms
46 msYour server sent the HTML in 46 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 30.5 s
30.5 sYour largest element takes 30.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
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: 13.8 s
13.8 sVisually, the page fills in at 13.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 6.5 s
6.5 sThe first text or image appears after 6.5 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.471
0.471The layout shifts by 0.471 while loading, so content jumps under the reader's thumb. Good is under 0.1.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Total Blocking Time: 3 ms
3 msScripts block the page for only 3 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.6 MB in 213 requests
4.6 MBYour homepage downloads 4.6 MB in 213 requests on a phone: scripts 2.2 MB (160), stylesheets 1.1 MB (18) and images 1.0 MB (10). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
slider1.jpg weighs 827 KiB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
758 KiB1 image is downloaded at several times the size a phone draws it, for example slider1.jpg at 3,840 px wide, shown at 371 px. Resized copies would save about 758 KiB.
5 images in older formats
5 images (999 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 1.3 g of CO₂ per visit
1.31 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.31 g of CO₂e: 157.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
Required ARIA attributes must be provided (1 element)
Required ARIA attributes must be provided: 1 element on the page fails this check, rated critical by axe-core.
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.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
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.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 10 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 10 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Blocked from indexing
Google's crawler is blocked from indexing this page.
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “ACE it! Spray on Polish: Best Spray Car Polish & Motorcycle Polish”.
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.
No XML sitemap
No XML sitemap at https://www.aceitpolish.com/sitemap.xml, so Google discovers your pages only by following links.
7 links crawlers can't follow
7 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
33 internal links, 3 external
The homepage links to 33 pages on aceitpolish.com and 3 external pages.
3 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “ACE it! Premium Spray on Polish - Get best deals on Spray Car Polish and Motorcycle Spray Polish for Long-lasting Showr…”.
One H1 headline
Your main headline reads: “Home Page”.
robots.txt in place
robots.txt is in place.
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.aceitpolish.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
15 internal pages checked
We fetched 15 pages linked from your homepage (of 19 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
20 of 23 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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 99 words
The homepage has only about 99 words of visible text; thin pages give Google and first-time buyers little to go on.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT US” and “SUBSCRIBE”.
6 calls to action
The homepage has 6 calls to action, for example “Sign up”, “CONTACT US” and “Subscribe”.
4 short forms
4 short forms (2 fields at most) are right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
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
17 cookies set on arrival
17Opening the homepage sets 17 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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 aceitpolish.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
- Liquid Web, L.L.C
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on aceitpolish.com, including 12 speed issues, 7 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.