findtimewatch.com website review

Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.

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

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

About 320 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

Shopify costs a phone 179 ms of main-thread work and 552 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.

8 third-party services load with your homepage (Shopify, cloudfront.net and etranslate.io and others), adding 948 KiB and 228 ms of main-thread time.

2 images could be 54 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

14 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “findtime smartwatch s46”.

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

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

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

Your homepage downloads 2.9 MB in 255 requests on a phone: other files 1.2 MB (134), scripts 815 KiB (54) and images 469 KiB (41). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (42 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

Structured data found (Organization) but with 2 problems, for example “Organization: missing name”.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

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

The homepage links to 90 pages on findtimewatch.com and 18 external pages.

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

/, /products/findtime-smartwatch-s46, /products/fitness-tracker-blood-pressure-heart-rate-monitor-blood-oxygen-activity-pedometer-big-fitness-tracker-sleep-monitor-for-women-men, /products/findtime-smartwatch-s43, /products/findtime-smartwatch-s51 and /products/womens-smart-watches-blood-pressure-monitor-ak15 and 9 others all use the title “user”. Search engines can't tell which page to show for a search, so each competes with the others.

/products/findtime-smartwatch-s46, /products/fitness-tracker-blood-pressure-heart-rate-monitor-blood-oxygen-activity-pedometer-big-fitness-tracker-sleep-monitor-for-women-men, /products/findtime-smartwatch-s43, /products/findtime-smartwatch-s51, /products/womens-smart-watches-blood-pressure-monitor-ak15 and /collections/sale and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

/products/findtime-smartwatch-s46, /products/fitness-tracker-blood-pressure-heart-rate-monitor-blood-oxygen-activity-pedometer-big-fitness-tracker-sleep-monitor-for-women-men, /products/findtime-smartwatch-s43, /products/findtime-smartwatch-s51, /products/womens-smart-watches-blood-pressure-monitor-ak15 and /collections/mens-watches and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

/pages/about-us took over 3 s to send its HTML from our server.

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

No viewport meta tag, so phones render the desktop layout zoomed out.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

4 errors were logged to the browser console while the page loaded, for example “Invalid left-hand side in assignment”.

1 link to other sites is dead, for example https://www.etranslate.io/?from=switcher (521).

HSTS is set, but max-age is 91 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.

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

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

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

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

findtimewatch.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

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: 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 Ads, 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 10 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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.