chimes.com website review

Not measured in this review.

• Tap response (INP) got 25% slower for real visitors

  +25%

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

• Largest content (LCP) held steady for real visitors

  +5%

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

• About 0.4 g of CO₂ per visit

  0.41 g

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

• 3 text elements with low contrast

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

  Elements (3)

• Hidden but focusable

  2 elements hidden from screen readers can still receive keyboard focus.

  Elements (2)

• All page content should be contained by landmarks (2 elements)

  All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  Elements (2)

• 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.

  Elements (1)

• 3 links without text

  3 visible links have no text or label, so screen readers cannot say where they go.

  Elements (3)

• 1 form field without a label

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

  View source

• Title is short (16 characters)

  Your title is only 16 characters: “Woodstock Chimes”. Between 30 and 65 characters leaves room to say what you do and for whom.

  View source

• 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 long (182 characters)

  Your meta description is 182 characters; Google truncates after about 160, so the end of your pitch is cut.

  View source

• One H1 headline

  Your <h1> is empty.

  View source

• 192 internal links, 15 external

  The homepage links to 192 pages on chimes.com and 15 external pages.

• 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.

• 1 page without a title

  /customer_authentication/redirect has no <title>, so Google invents the link text in results.

  Elements (1)

• 1 linked page hidden from search

  /customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  Elements (1)

• 4 pages without a meta description

  /collections/all, /collections/sale, /customer_authentication/redirect and /collections/new-arrivals have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (4)

• 1 page without an H1

  /customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

• 15 internal pages checked

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

• 6 JavaScript errors while loading

  6 errors were logged to the browser console while the page loaded, for example “gtag is not defined”.

• Short HSTS lifetime

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

• 1 link through redirect chains

  1 link go through two or more redirects, for example https://chimes.com/customer_authentication/redirect?locale=en&region_country=US.

• No Referrer-Policy

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

• No Permissions-Policy

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

• Deprecated X-XSS-Protection

  X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

• No security.txt

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

• No CAA record

  chimes.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.

• DNSSEC is off

  chimes.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.

• Thin social proof

  Social proof on the homepage: 147 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

• No direct contact details

  No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

• 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 1,301 words of copy

  The homepage carries about 1,301 words of visible text.

• No DKIM key on the usual selectors

  We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

• Email authentication score: 75/100

  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.

• 6 trackers load before any consent

  6

  Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, HubSpot, Klaviyo and Meta Pixel and 1 more (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.

• 21 cookies set on arrival

  21

  Opening the homepage sets 21 cookies, 6 of them by other companies (measured from a US location before any click).

• 43 other companies contacted

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