novelkeys.com website review

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

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

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

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

8 third-party services load with your homepage (uploadly-cdn.com, Amazon Web Services and Shopify and others), adding 392 KiB and 466 ms of main-thread time.

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

15 images could be 185 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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 11.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “MTNU DASHER PREORDER!”.

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

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

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

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

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

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

Your homepage downloads 2.5 MB in 244 requests on a phone: images 1.0 MB (93), other files 694 KiB (83) and scripts 558 KiB (52). Under 2 MB keeps phones on slow connections fast.

9 images further down the page (271 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (33 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

Your title is 82 characters, so Google will cut it off around 60: “Custom Mechanical Keyboards, Keycaps, Switches, Deskpads, and More – NovelKeys LLC”.

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

The homepage links to 83 pages on novelkeys.com and 13 external pages.

https://novelkeys.com/collections/gmk, https://novelkeys.com/collections/double-shot-abs, https://novelkeys.com/collections/dyesub-pbt, https://novelkeys.com/collections/extras-preorder, https://novelkeys.com/collections/merch and https://novelkeys.com/products/gmk-mtnu-dasher-keycaps and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://novelkeys.com/collections/frontpage/products/matrix-carnival-keyboard, whose canonical is https://novelkeys.com/products/matrix-carnival-keyboard. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

1 error was logged to the browser console while the page loaded, for example “Uncaught Error: Goaffpro is already loaded. This message prevents duplicate loading of the script. Kindly ignore.”.

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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

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

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Tag Manager, Meta Pixel and TikTok Pixel (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 9 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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.