supanext.com website review

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

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

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

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

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

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

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

3 third-party services load with your homepage (lmsqueezy.com, Plausible and lemonsqueezy.com), adding 21 KiB and 7 ms of main-thread time.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 4.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Save 55+ hours of work with a complete Nextjs Supabase Star…”. Most of its time is element render delay (3.2 s).

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

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

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 4.2 MB in 28 requests on a phone: media 3.8 MB (2), scripts 222 KiB (14) and images 109 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

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

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

The homepage links to 12 pages on supanext.com and 8 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 https://www.supanext.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://www.supanext.com/validate-license all use the title “Supanext - Nextjs Supabase SaaS Starter”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.supanext.com/blog has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.supanext.com/contact and https://www.supanext.com/validate-license have 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 6 pages linked from your homepage and read each the way a search engine does.

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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