Website review, no card needed
acesouthern.com website review
Visit site (opens in a new tab)Reviewed 18 October 202650 issues · 94 checks
This review found 50 issues worth fixing on acesouthern.com, 21 of them high impact, across 94 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 3.7 s |
| May 2, 2026 | 3.7 s |
| May 9, 2026 | 3.6 s |
| May 16, 2026 | 3.5 s |
| May 23, 2026 | 3.5 s |
| May 30, 2026 | 3.6 s |
| Jun 6, 2026 | 3.5 s |
| Jun 13, 2026 | 3.5 s |
| Jun 20, 2026 | 3.5 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.4 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 118 ms |
| May 2, 2026 | 117 ms |
| May 9, 2026 | 114 ms |
| May 16, 2026 | 117 ms |
| May 23, 2026 | 120 ms |
| May 30, 2026 | 121 ms |
| Jun 6, 2026 | 121 ms |
| Jun 13, 2026 | 121 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 120 ms |
| Jul 4, 2026 | 121 ms |
| Jul 11, 2026 | 120 ms |
| Jul 18, 2026 | 119 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 120 ms |
| Aug 8, 2026 | 120 ms |
| Aug 15, 2026 | 121 ms |
| Aug 22, 2026 | 120 ms |
| Aug 29, 2026 | 113 ms |
| Sep 5, 2026 | 111 ms |
| Sep 12, 2026 | 109 ms |
| Sep 19, 2026 | 112 ms |
| Sep 26, 2026 | 113 ms |
| Oct 3, 2026 | 115 ms |
| Oct 10, 2026 | 115 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.3 s
2.6 s
4.0 s
5.3 s
6.6 s
8.0 s
9.3 s
10.6 s
Speed
Reduce unused JavaScript
5.5 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.5 s faster on a phone.
Use efficient cache lifetimes
1.9 s · 625 KiB37 files are served with short cache lifetimes, so returning visitors download them again (625 KiB).
Main-thread work: 11.0 s
A phone's processor spends 11.0 s on main-thread work while loading, 7.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 22
22/100Your mobile performance score is 22 (desktop: 35). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5,454 HTML elements
The page has 5,454 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 1.1 s. During a long task the page ignores taps.
8 third-party services on the page
8 third-party services load with your homepage (niceincontact.com, Google Tag Manager and PowerReviews and others), adding 1.1 MB and 554 ms of main-thread time.
Reduce unused CSS
300 ms · 164 KiBAbout 164 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Improve image delivery
300 ms · 57 KiB5 images could be 57 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Legacy JavaScript
300 ms · 55 KiBPolyfills for old browsers add 55 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
niceincontact.com adds 242 ms
242 msniceincontact.com costs a phone 242 ms of main-thread work and 342 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
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 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: 175 ms
175 msYour server sent the HTML in 175 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 FCP: 3.2 s
3.2 sReal visitors see the first content after 3.2 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 22.6 s
22.6 sYour largest element takes 22.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 15.7 s
15.7 sVisually, the page fills in at 15.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 26.9 s
26.9 sThe page becomes fully interactive after 26.9 s. Good is under 3.8 s.
Total Blocking Time: 3.7 s
3.7 sScripts block taps and scrolling for 3.7 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.4 s
3.4 sReal visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.192
0.192The layout shifts by 0.192 while loading, so content jumps under the reader's thumb. Good is under 0.1.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 118 ms to 115 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 115 ms
115 msReal visitors wait 115 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 3.7 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 4.1 MB in 141 requests
4.1 MBYour homepage downloads 4.1 MB in 141 requests on a phone: scripts 2.7 MB (48), images 683 KiB (34) and HTML 316 KiB (4). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
HS_Global_EN_Icon_GEP_pdp-banner-lady-image.svg weighs 538 KiB. On a phone connection a single image that size takes seconds.
About 1.2 g of CO₂ per visit
1.18 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.18 g of CO₂e: 141.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Links must have discernible text (2 elements)
Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (17 elements)
All page content should be contained by landmarks: 17 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate 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.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Headings should not be empty (3 elements)
Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 256 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 8 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Page is set to noindex
The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Blocked from indexing
Google's crawler is blocked from indexing this page.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (25 characters)
Your meta description is only 25 characters: “You’re in the right place”. 70 to 160 characters is enough to sell the click.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1,447 internal links, 77 external
The homepage links to 1,447 pages on acesouthern.com and 77 external pages.
5 checks passed
Title: 34 characters
Your title is a healthy 34 characters: “ACE SOUTHERN | Now on Henry Schein”.
Canonical URL set
The canonical URL is https://www.henryschein.com/en-us/supplies/acclean.
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.henryschein.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.henryschein.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 (2,676 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://www.henryschein.com/en-us/supplies/en-us, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page without a title
https://www.henryschein.com/en-us/c/supplies/acrylics/denture-resins has no <title>, so Google invents the link text in results.
8 linked pages hidden from search
https://www.henryschein.com/en-us/about/contact, https://www.henryschein.com/en-us/c/supplies/3d-printing, https://www.henryschein.com/en-us/c/supplies/3d-printing/resins-and-resin-bundles, https://www.henryschein.com/en-us/c/supplies/abrasives/aluminum-oxide, https://www.henryschein.com/en-us/c/supplies/abrasives/discs and https://www.henryschein.com/en-us/c/supplies/acrylics and 2 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages without a meta description
https://www.henryschein.com/en-us/c/supplies/abrasives/aluminum-oxide and https://www.henryschein.com/en-us/c/supplies/acrylics/denture-resins have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.henryschein.com/en-us/product/office-supplies, whose canonical is https://www.henryschein.com/en-us/product/us-prd-henryschein.com/en-us/product/office-suppliesen-us/product/office-supplies. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
9 pages without an H1
https://www.henryschein.com/en-us/about/contact, https://www.henryschein.com/en-us/product/office-supplies, https://www.henryschein.com/en-us/c/supplies/3d-printing, https://www.henryschein.com/en-us/c/supplies/3d-printing/resins-and-resin-bundles, https://www.henryschein.com/en-us/c/supplies/abrasives/aluminum-oxide and https://www.henryschein.com/en-us/c/supplies/abrasives/discs and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.henryschein.com/en-us/product/office-supplies has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
3 pages slow to respond
https://www.henryschein.com/en-us/product/office-supplies, https://www.henryschein.com/en-us/c/supplies/abrasives/aluminum-oxide and https://www.henryschein.com/en-us/c/supplies/acrylics/denture-resins took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 195 found) and read each the way a search engine does.
1 checks passed
Titles are unique
Every page we checked has its own title.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'addEventListener')”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
7 of 8 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.
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.
Thin social proof
Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
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 266 words of copy
The homepage carries about 266 words of visible text.
4 checks passed
13 calls to action
The homepage has 13 calls to action, for example “Contact”, “Order From History” and “Request A Quote”.
2 short forms
2 short forms (0 fields at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 3 phone links and 3 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.
18 cookies set on arrival
18Opening the homepage sets 18 cookies (measured from a US location before any click).
16 other companies contacted
Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Usercentrics
A consent management tool (Usercentrics) 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 acesouthern.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Angular
- Hosting
- Azure
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 acesouthern.com, including 22 speed issues, 6 SEO issues and 4 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.