nextsaas.live website review

7 images could be 476 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.

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

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

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

Google Tag Manager costs a phone 281 ms of main-thread work and 353 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.

5 third-party services load with your homepage (Google Tag Manager, promotekit.com and Google/Doubleclick Ads and others), adding 408 KiB and 322 ms of main-thread time.

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

1 file is served with short cache lifetimes, so returning visitors download them again (43 KiB).

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

Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

23 KiB could be saved by minifying JavaScript.

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 12.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “NextSaaS Logo”.

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

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

Scripts block taps and scrolling for 289 ms in total while the page loads. Good is under 200 ms.

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 2.1 MB in 89 requests on a phone: images 1.2 MB (46), scripts 668 KiB (30) and fonts 188 KiB (2). Under 2 MB keeps phones on slow connections fast.

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

1 image is downloaded at several times the size a phone draws it, for example daniel.png at 400 px wide, shown at 45 px. Resized copies would save about 55 KiB.

3 images (127 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 0.60 g of CO₂e: 72.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 link inside paragraphs relies on colour alone to stand out.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

Headings should not be empty: 3 elements on the page fail 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 (h1 → h3 and h2 → h4), 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.

There are 2 <h1> headlines (“The All-In-One Boilerplate to Transform Your Prod…” and “Launch your MVP in weeks hours”). One clear main headline is easier for people and search engines.

The homepage links to 32 pages on nextsaas.live and 15 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://nextsaas.live/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.

https://nextsaas.live/testimonial has no <title>, so Google invents the link text in results.

https://nextsaas.live/posts, https://nextsaas.live/posts/maximize-website-performance-with-next-js-and-nextsaas, https://nextsaas.live/redeem, https://nextsaas.live/pages/privacy-policy and https://nextsaas.live/pages/terms-and-conditions declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

/, https://nextsaas.live/posts and https://nextsaas.live/redeem all use the title “NextSaaS - Elevate Your Product to SaaS in Hours!”. Search engines can't tell which page to show for a search, so each competes with the others.

https://nextsaas.live/testimonial has no meta description, so Google writes the search snippet from whatever text it finds.

https://nextsaas.live/docs, https://nextsaas.live/posts, https://nextsaas.live/docs/authentication, https://nextsaas.live/docs/payments, https://nextsaas.live/docs/theme and https://nextsaas.live/docs/database and 4 others use the same meta description. A description written for each page earns more clicks.

https://nextsaas.live/testimonial and https://nextsaas.live/redeem have no <h1> headline, so visitors and search engines get no clear main topic.

https://nextsaas.live/testimonial and https://nextsaas.live/redeem 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 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.

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

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

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

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