safcodental.com website review

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

20 files are served with short cache lifetimes, so returning visitors download them again (728 KiB).

Google Tag Manager costs a phone 1.8 s of main-thread work and 860 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

A phone's processor spends 11.4 s on main-thread work while loading, 6.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Your mobile performance score is 30 (desktop: 50). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Hubspot and others), adding 2.4 MB and 3.2 s of main-thread time.

About 116 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 700 ms faster on a phone.

20 long tasks block the main thread while loading, the longest for 735 ms. During a long task the page ignores taps.

12 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.

Google CDN costs a phone 545 ms of main-thread work and 738 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.

22 images could be 494 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Hubspot costs a phone 336 ms of main-thread work and 315 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.

The page has 2,729 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

17 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 11.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Shop Now”.

The page becomes fully interactive after 30.6 s. Good is under 3.8 s.

Scripts block taps and scrolling for 3.7 s in total while the page loads. Good is under 200 ms.

Visually, the page fills in at 7.9 s (Speed Index). Good is under 3.4 s.

The first text or image appears after 3.5 s on a phone. Good is under 1.8 s.

Real visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.

Real visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 141 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.0 MB in 207 requests on a phone: scripts 2.8 MB (63), images 1.4 MB (75) and other files 398 KiB (54). Under 2 MB keeps phones on slow connections fast.

3 images further down the page (225 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 1.43 g of CO₂e: 171.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Links must have discernible text: 3 elements on the page fail this check, rated serious by axe-core.

Some list items are not inside a list.

Some lists contain elements other than list items, which screen readers announce wrongly.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

3 images have no alt text, which hurts accessibility and image search.

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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

30 links have no real href, so search engines can't follow them.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 738 pages on safcodental.com and 13 external pages.

There is no https://www.safcodental.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.

https://www.safcodental.com/temporary-search-pages/lasting-impressions and https://www.safcodental.com/celebrate-healthy-smiles are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.safcodental.com/contact, whose canonical is https://www.safcodental.com/contact-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.safcodental.com/temporary-search-pages/lasting-impressions, https://www.safcodental.com/celebrate-healthy-smiles, https://www.safcodental.com/contact, https://www.safcodental.com/catalog, https://www.safcodental.com/catalog/acrylics-and-reline and https://www.safcodental.com/catalog/anesthetics and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.safcodental.com/contact, https://www.safcodental.com/catalog, https://www.safcodental.com/catalog/acrylics-and-reline, https://www.safcodental.com/catalog/anesthetics, https://www.safcodental.com/catalog/burs-and-diamonds and https://www.safcodental.com/catalog/cad-cam and 7 others have 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.

We fetched 15 pages linked from your homepage (of 162 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56014379&tm=gtm002&Ver=2&mid=9338bac9-05fb-4bd6-b7bc-e91fb35a4147&bo=1&sid=e0ad5fa0d07e11f1ae8fb1f2bab2f673&vid=e0ad8860d07e11f191a36be1e3944005&vids=1&msclkid=N&pi=91.

15 of 54 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 546 words of visible text.

Before a visitor clicks anything, the page loads FullStory, Google Ads, Google Analytics, Google Tag Manager and HubSpot 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.

Opening the homepage sets 19 cookies (measured from a US location before any click).

Loading the homepage contacts 44 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.