detering.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 6.9 s faster on a phone.

10 images could be 977 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

14 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.

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

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

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

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

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

Squarespace costs a phone 737 ms of main-thread work and 1.4 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.

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

Polyfills for old browsers add 132 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

squarespace-cdn.com costs a phone 0 ms of main-thread work and 1.3 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.

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

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.

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

Your largest element takes 22.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FAMILY-OWNED AND OPERATED DISTRIBUTOR OF DOORS, WINDOWS, MI…”.

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

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

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

The layout shifts by 0.117 while loading, so content jumps under the reader's thumb. Good is under 0.1.

1 image have no width and height attributes, so the layout jumps as each one loads.

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.

Your homepage downloads 4.4 MB in 97 requests on a phone: scripts 2.3 MB (54), images 1.2 MB (15) and other files 468 KiB (7). Under 2 MB keeps phones on slow connections fast.

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

Page should contain a level-one heading: 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.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Structured data found (LocalBusiness and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/67c0cb123bb85d5709f…”.

The homepage links to 66 pages on detering.com and 12 external pages.

Your Organization JSON-LD is missing name, url, logo, 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.

There is no /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.

/doors and /products all use the title “Doors | Enhance Your Entry — The Detering Company”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/doors and /products use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /products, whose canonical is /doors. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/mouldings, /stair-parts, /lumber, /custom, /projects and /about and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

/mouldings, /stair-parts, /lumber, /custom, /projects and /about and 2 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 16 found) and read each the way a search engine does.

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/67c0cb123bb85d5709fa1f99/263/5c5…”.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

HSTS is set, but max-age is 180 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

detering.com is registered until Nov 2026. Make sure auto-renew is on and the card on file is current.

detering.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

detering.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 623 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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.

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