Website review, no card needed
xtremepolishingsystems.com website review
Visit site (opens in a new tab)Reviewed 19 November 202632 issues · 81 checks
This review found 32 issues worth fixing on xtremepolishingsystems.com, 13 of them high impact, across 81 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
74C- #84,153 of 120,066 reviewed websitesbeats 26%
- #53,208 of 68,040 online storesbeats 18%
- #50,057 of 62,009 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
| Nov 7, 2026 | 1.4 s |
| Nov 14, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 192 ms |
| Jun 6, 2026 | 197 ms |
| Jun 13, 2026 | 204 ms |
| Jun 20, 2026 | 212 ms |
| Jun 27, 2026 | 211 ms |
| Jul 4, 2026 | 212 ms |
| Jul 11, 2026 | 213 ms |
| Jul 18, 2026 | 215 ms |
| Jul 25, 2026 | 219 ms |
| Aug 1, 2026 | 221 ms |
| Aug 8, 2026 | 232 ms |
| Aug 15, 2026 | 241 ms |
| Aug 22, 2026 | 254 ms |
| Aug 29, 2026 | 278 ms |
| Sep 5, 2026 | 297 ms |
| Sep 12, 2026 | 313 ms |
| Sep 19, 2026 | 331 ms |
| Sep 26, 2026 | 343 ms |
| Oct 3, 2026 | 343 ms |
| Oct 10, 2026 | 343 ms |
| Oct 17, 2026 | 331 ms |
| Oct 24, 2026 | 313 ms |
| Oct 31, 2026 | 304 ms |
| Nov 7, 2026 | 288 ms |
| Nov 14, 2026 | 271 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.2 s
2.4 s
3.7 s
4.9 s
6.1 s
7.3 s
8.6 s
9.8 s
Speed
Reduce unused JavaScript
3.1 s · 1.1 MBAbout 1.1 MB 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.
Main-thread work: 10.5 s
A phone's processor spends 10.5 s on main-thread work while loading, 3.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 38
38/100Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Shopify and others), adding 2.4 MB and 2.0 s of main-thread time.
Use efficient cache lifetimes
800 ms · 659 KiB26 files are served with short cache lifetimes, so returning visitors download them again (659 KiB).
Improve image delivery
650 ms · 669 KiB9 images could be 669 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.
Google Tag Manager adds 647 ms
647 msGoogle Tag Manager costs a phone 647 ms of main-thread work and 983 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.
Render-blocking requests
450 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Shopify adds 267 ms
267 msShopify costs a phone 267 ms of main-thread work and 787 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 316 ms
316 msFacebook costs a phone 316 ms of main-thread work and 258 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,138 HTML elements
The page has 2,138 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 208 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 51 KiBPolyfills for old browsers add 51 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
38 KiBAbout 38 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
7 KiB7 KiB could be saved by minifying JavaScript.
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: 14 ms
14 msYour server sent the HTML in 14 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: 23.6 s
23.6 sYour largest element takes 23.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 28.1 s
28.1 sThe page becomes fully interactive after 28.1 s. Good is under 3.8 s.
First Contentful Paint: 4.8 s
4.8 sThe first text or image appears after 4.8 s on a phone. Good is under 1.8 s.
Speed Index: 9.5 s
9.5 sVisually, the page fills in at 9.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 785 ms
785 msScripts block taps and scrolling for 785 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 208 ms
208 msReal visitors wait 208 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 44% slower for real visitors
+44%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 192 ms to 271 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 514 ms
514 msReal visitors wait 514 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.8 MB in 545 requests
6.8 MBYour homepage downloads 6.8 MB in 545 requests on a phone: scripts 2.8 MB (184), images 2.2 MB (27) and other files 1.5 MB (310). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
385 KiB1 image is downloaded at several times the size a phone draws it, for example 1769004720778-Logo_XPS 320x260.png at 1,334 px wide, shown at 200 px. Resized copies would save about 385 KiB.
1 image in older formats
1 image (482 KiB) is 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.9 g of CO₂ per visit
1.94 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.94 g of CO₂e: 232.8 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
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
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.
Headings skip levels
Headings skip levels (h1 → h3), 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. (4 elements).
2 checks passed
Every image has alt text
All 74 images in the HTML carry an alt attribute.
12 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 14 WCAG 2.2 A/AA and best-practice rules on the phone render: 12 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
277 internal links, 16 external
The homepage links to 277 pages on xtremepolishingsystems.com and 16 external pages.
8 checks passed
Meta description: 121 characters
Your meta description is 121 characters: “We offer industrial epoxy resin coatings, surface prep equipment, floor machines, and decorative concrete floor supplie…”.
One H1 headline
Your main headline reads: “Xtreme Polishing Systems”.
Title: 61 characters
Your title is a healthy 61 characters: “Xtreme Polishing Systems | Epoxy & Concrete Contractor Supply”.
Canonical URL set
The canonical URL is https://xtremepolishingsystems.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization 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://xtremepolishingsystems.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
llms.txt published
The site publishes https://xtremepolishingsystems.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 137 found) and read each the way a search engine does.
7 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.
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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187054084&Ver=2&mid=a5bfbac3-de60-487e-b7c1-a8d595f391a1&bo=1&sid=4fa0e5a0e47411f1b5648320695dcbcf&vid=4fa10600e47411f1b821296ca80f332b&vids=1&msclkid=N&pi=918639831&l.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Only about 31 words
The homepage has only about 31 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
24 calls to action
The homepage has 24 calls to action, for example “Shop”, “Bulk Pricing” and “Join Epoxy Network”.
11 short forms
11 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity, HubSpot and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 4 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
45 cookies set on arrival
45Opening the homepage sets 45 cookies, 6 of them by other companies (measured from a US location before any click).
50 other companies contacted
Loading the homepage contacts 50 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) 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 xtremepolishingsystems.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Blockify Fraud Filter · Orderlogic Min Max Limits · Eg Auto Add To Cart · Frequently Bought · Simple Affiliate · Region Restrictions · Glo Color Swatch · orderlogicapp.com · loox.io · trafficmanager.net · hubapi.com · bestfreecdn.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify Hosted
Company
- Employees
- 83
- Headquarters
- Pompano Beach
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on xtremepolishingsystems.com, including 19 speed issues, 1 SEO issue 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.