corvi.com website review

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

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

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

133 files are served with short cache lifetimes, so returning visitors download them again (257.9 MB).

23 images could be 9.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Cloudflare CDN, website-files.com and Google Tag Manager and others), adding 44.9 MB and 572 ms of main-thread time.

website-files.com costs a phone 211 ms of main-thread work and 44.3 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.

Your mobile performance score is 57 (desktop: 71). Pages that score under 90 lose visitors before the first paint.

About 15 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.

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

About 95 KiB of JavaScript is downloaded but never used on this page.

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

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

Your largest element takes 10.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Revolutionizing LED Design for Efficiency, Durability and S…”.

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

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

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

16 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 264.9 MB in 227 requests on a phone: media 153.2 MB (51), images 110.7 MB (119) and fonts 400 KiB (21). Under 2 MB keeps phones on slow connections fast.

40 images weigh 93.6 MB together. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example 6901a73b1b20bcc2d7df2464_Bulb life edited (2).gif at 1,152 px wide, shown at 362 px. Resized copies would save about 3.7 MB.

40 images (93.6 MB) 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.

2 images further down the page (4.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

32 buttons have no accessible name, so screen readers announce just “button”.

32 tap targets are too small or too close together to hit reliably with a finger.

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

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

All page content should be contained by landmarks: 49 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.

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

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

Headings skip levels (h1 → h3, 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: “home”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“Revolutionizing LED Design for Efficiency, Durabi…” and “Why Corvi lights have 5X Longer Life”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

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

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

There is no robots.txt at corvi.com/robots.txt, the first file search crawlers ask for.

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

The homepage links to 24 pages on corvi.com and 19 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

/about, /product-new, /web-warranty, /documents, /terms and /privacy-policy and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

/product-new has no <h1> headline, so visitors and search engines get no clear main topic.

/documents has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

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.

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

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

corvi.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: 18 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

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 1,297 words of visible text.

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