knightwatchcollection.com website review

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

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

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

8 third-party services load with your homepage (YouTube, tidio.co and Shopify and others), adding 1.7 MB and 602 ms of main-thread time.

YouTube costs a phone 465 ms of main-thread work and 991 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.

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

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

tidio.co costs a phone 86 ms of main-thread work and 515 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.

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

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

1 image could be 7 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

3 KiB could be saved by minifying JavaScript.

Your largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

4 images 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 3.5 MB in 205 requests on a phone: scripts 1.5 MB (55), other files 797 KiB (115) and images 683 KiB (17). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (78 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.98 g of CO₂e: 118.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 frame has no title, so screen-reader users cannot tell what it contains.

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

1 image has no alt text, which hurts accessibility and image search.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is 80 characters, so Google will cut it off around 60: “Buy, Sell & Trade Luxury Watches - Buy Luxury Timepiece– Knight Watch Collection”.

Structured data found (Organization and WebSite) but with 1 problem, for example “ld+json block 1 is not valid JSON (Bad control character in string literal in JSON at position )”.

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

The homepage links to 41 pages on knightwatchcollection.com and 4 external pages.

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

/collections/bell-rose/products/bell-ross-br0392-green-bronze-diver and /products/bell-ross-br0392-green-bronze-diver all use the title “Bell & Ross BR0392 Green Bronze Diver– Knight Watch Collection”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/pages/membership, /pages/wishlist, /collections/omega and /pages/contact-us have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/bell-rose/products/bell-ross-br0392-green-bronze-diver and /products/bell-ross-br0392-green-bronze-diver use the same meta description. A description written for each page earns more clicks.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example /collections/bell-rose/products/bell-ross-br0392-green-bronze-diver, whose canonical is /products/bell-ross-br0392-green-bronze-diver. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/pages/membership, /pages/about-us and /pages/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage and read each the way a search engine does.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

Chrome logged issues while loading the page (“Cookie”).

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

3 links go through two or more redirects, for example https://www.facebook.com/sharer.php?u=https://knightwatchcollection.com/products/cartier-calibre-de-cartier-w7100037.

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.

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

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

Social proof on the homepage: 2 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.

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

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

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

Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 a mx ptr include:bluehost.com ?all”.

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 8 cookies, 1 of them by other companies (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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.