Website review, no card needed

american-time.com logo

american-time.com website review

Visit site (opens in a new tab)Reviewed 19 October 202638 issues · 85 checks

This review found 38 issues worth fixing on american-time.com, 17 of them high impact, across 85 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.5 s2.5 sApr 25Oct 103.3 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20263.3 s
May 2, 20263.9 s
May 9, 20264.2 s
May 16, 20264.3 s
May 23, 20264.2 s
May 30, 20263.9 s
Jun 6, 20263.6 s
Jun 13, 20263.5 s
Jun 20, 20263.7 s
Jun 27, 20263.5 s
Jul 4, 20263.5 s
Jul 11, 20263.2 s
Jul 18, 20263.1 s
Jul 25, 20262.9 s
Aug 1, 20262.8 s
Aug 8, 20262.7 s
Aug 15, 20262.7 s
Aug 22, 20262.7 s
Aug 29, 20262.8 s
Sep 5, 20262.8 s
Sep 12, 20263.0 s
Sep 19, 20263.1 s
Sep 26, 20263.3 s
Oct 3, 20263.3 s
Oct 10, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
136 ms75 msApr 25Oct 10129 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202683 ms
May 2, 202686 ms
May 9, 202687 ms
May 16, 202690 ms
May 23, 202696 ms
May 30, 202696 ms
Jun 6, 202696 ms
Jun 13, 202695 ms
Jun 20, 202695 ms
Jun 27, 202695 ms
Jul 4, 202690 ms
Jul 11, 202699 ms
Jul 18, 202699 ms
Jul 25, 202699 ms
Aug 1, 202696 ms
Aug 8, 202684 ms
Aug 15, 202682 ms
Aug 22, 202687 ms
Aug 29, 202688 ms
Sep 5, 202696 ms
Sep 12, 2026110 ms
Sep 19, 2026111 ms
Sep 26, 2026117 ms
Oct 3, 2026129 ms
Oct 10, 2026129 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

Full-page screenshot of american-time.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. american-time.com at 1.0 s1.0 s
  2. american-time.com at 2.1 s2.1 s
  3. american-time.com at 3.1 s3.1 s
  4. american-time.com at 4.2 s4.2 s
  5. american-time.com at 5.2 s5.2 s
  6. american-time.com at 6.3 s6.3 s
  7. american-time.com at 7.3 s7.3 s
  8. american-time.com at 8.3 s8.3 s

Speed

13 to fix29
  • Render-blocking requests

    3.0 s

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

  • Use efficient cache lifetimes

    1.6 s · 576 KiB

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

  • Reduce unused CSS

    1.9 s · 162 KiB

    About 162 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.9 s faster on a phone.

  • Reduce unused JavaScript

    1.2 s · 792 KiB

    About 792 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 29

    29/100

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

  • Main-thread work: 7.0 s

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

  • 3,580 HTML elements

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

  • 8 third-party services on the page

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

  • Google CDN adds 931 ms

    931 ms

    Google CDN costs a phone 931 ms of main-thread work and 1.1 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 Tag Manager adds 691 ms

    691 ms

    Google Tag Manager costs a phone 691 ms of main-thread work and 350 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.

  • 20 long tasks on the main thread

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

  • Facebook adds 435 ms

    435 ms

    Facebook costs a phone 435 ms of main-thread work and 211 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.

  • Hubspot adds 361 ms

    361 ms

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

  • Legacy JavaScript

    150 ms · 63 KiB

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

  • Minify JavaScript

    150 ms · 11 KiB

    11 KiB could be saved by minifying JavaScript.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Phones get a much slower page than desktops

    Desktop scores 62 but mobile only 29. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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: 9 ms

    9 ms

    Your server sent the HTML in 9 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix100
  • 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: 14.6 s

    14.6 s

    Your largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “One Clock. One Setup. Done. Our Economical Stand Alone cloc…”.

  • Time to Interactive: 21.2 s

    21.2 s

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

  • First Contentful Paint: 5.5 s

    5.5 s

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

  • Total Blocking Time: 2.1 s

    2.1 s

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

  • Speed Index: 9.8 s

    9.8 s

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

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

    +53%

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

3 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user CLS: 0.01

    0.01

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 3.7 MB in 135 requests

    3.7 MB

    Your homepage downloads 3.7 MB in 135 requests on a phone: scripts 2.2 MB (68), images 499 KiB (24) and other files 377 KiB (22). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    1.04 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.04 g of CO₂e: 124.2 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

5 to fixGoogle 9694
  • 8 text elements with low contrast

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

  • 14 images without alt text

    14 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)

    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.

  • 1 form field without a label

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

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and 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. (2 elements).

1 checks passed
  • 53 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9284
  • 8 H1 headlines

    There are 8 <h1> headlines (“One Clock. One Setup. Done.”, “Find the Exact Part You Need Fast.” and “Still Using an Outdated Clock System? We’ve Got t…”). One clear main headline is easier for people and search engines.

  • Meta description is long (193 characters)

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

  • Structured data has 8 problems

    Structured data found (BreadcrumbList, ImageObject, Organization and SiteNavigationElement) but with 8 problems, for example “SiteNavigationElement: url is not an absolute URL ("#")”.

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

  • 336 internal links, 9 external

    The homepage links to 336 pages on american-time.com and 9 external pages.

5 checks passed
  • Title: 63 characters

    Your title is a healthy 63 characters: “Synchronized Clock Systems - Replacement Clocks | American Time”.

  • Canonical URL set

    The canonical URL is https://www.american-time.com/.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.american-time.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,333 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 3 pages without a meta description

    https://www.american-time.com/value-added-resellers-program, https://www.american-time.com/american-time-partners and https://www.american-time.com/communication-systems/everalert-speaker have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.american-time.com/which-synchronized-clock-system-is-right-for-you and https://www.american-time.com/value-added-resellers-program have 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 69 found) and read each the way a search engine does.

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

  • Titles are unique

    Every page we checked has its own title.

  • 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

3 to fixGoogle 9276
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343050532&Ver=2&mid=fbc6eeaf-498f-49f8-b272-51685e1bc492&bo=1&sid=d9a33c90cb9411f1ae252118839ad43e&vid=d9a34d80cb9411f198de3b6eb77e69d0&vids=1&msclkid=N&pi=918639831&l.

  • 6 small tap targets

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • No social proof

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

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP PARTS & ACCESSORIES” and “SHOP CLOCKS”.

  • 22 calls to action

    The homepage has 22 calls to action, for example “Learn More”, “Shop” and “Get In Touch”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

Privacy and tracking

  • 7 trackers load before any consent

    7

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

  • 16 cookies set on arrival

    16

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

  • 38 other companies contacted

    Loading the homepage contacts 38 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 american-time.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on american-time.com, including 22 speed issues, 4 SEO issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25