noirvere.com website review

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

8 third-party services load with your homepage (Clarity, Shopify and Google Tag Manager and others), adding 1.6 MB and 1.0 s of main-thread time.

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

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

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

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

Clarity costs a phone 384 ms of main-thread work and 29 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.

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

azurefd.net costs a phone 30 ms of main-thread work and 323 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 63 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

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.

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

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

Visually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 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 120 ms to 146 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 1.8 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.3 MB in 443 requests on a phone: scripts 1.5 MB (129), other files 1.4 MB (265) and images 844 KiB (22). Under 2 MB keeps phones on slow connections fast.

10 images (409 KiB) are 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 1.20 g of CO₂e: 144.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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.

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

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

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 → h5), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

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

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

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://noirvere.com/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 69 pages on noirvere.com and 3 external pages.

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

There is no https://noirvere.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.

/ and https://noirvere.com/apps/track123 all use the title “Noirvere”. Search engines can't tell which page to show for a search, so each competes with the others.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://noirvere.com/collections/unsere-bags, whose canonical is https://noirvere.com/collections/vegan-leather-bags. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://noirvere.com/collections/unsere-bags, https://noirvere.com/apps/track123, https://noirvere.com/pages/contact, https://noirvere.com/collections/most-wanted and https://noirvere.com/collections/everyday-bb-bag-shape have no <h1> headline, so visitors and search engines get no clear main topic.

https://noirvere.com/apps/track123 took over 3 s to send its HTML from our server.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_EMPTY_RESPONSE”.

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

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.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 325 words of visible text.

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