nexaflow.net website review

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

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

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

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

1 third-party service load with your homepage (Google Tag Manager), adding 153 KiB and 99 ms of main-thread time.

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

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors wait 4.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 4.5 s (75th percentile). Good is under 1.8 s.

Real visitors wait 3.2 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Real visitors wait 228 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

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

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

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

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: 26 elements on the page fail this check, rated moderate by axe-core.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 21 characters: “nexaflow.net | fruits”. 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.

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

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

No XML sitemap at https://www.fruits.co/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 5 pages on nexaflow.net and 2 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.fruits.co/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://www.fruits.co/terms, https://www.fruits.co/privacy and https://www.fruits.co/legal-notice have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.fruits.co/privacy has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

Large scripts ship without source maps.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage has only about 216 words of visible text; thin pages give Google and first-time buyers little to go on.

Before a visitor clicks anything, the page loads 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.

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