csvbox.io website review

Your mobile performance score is 95. That is in Google's “good” band (90 and up).

A phone's processor spends 0.6 s on main-thread work while loading, 121 ms of it running JavaScript. That is comfortably low.

Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

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

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

For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

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

Your largest element renders in 2.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Ship CSV imports in an afternoon. Not next quarter.”.

The page is fully interactive after 2.3 s.

The layout barely moves while loading (CLS 0, good is under 0.1).

Scripts block the page for only 12 ms while loading. Good is under 200 ms.

Your homepage downloads 347 KiB in 33 requests on a phone: fonts 124 KiB (4), scripts 100 KiB (8) and images 86 KiB (13). That is a lean page.

Every sizeable image is WebP, AVIF or SVG.

Images below the first screen wait until the visitor scrolls to them.

No image is downloaded at more than three times the size it is drawn on a phone.

All 35 images in the HTML carry an alt attribute.

axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

Your main headline reads: “Ship CSV imports in an afternoon. Not next quarter.”.

Your title is a healthy 52 characters: “CSVbox — The Fast CSV Importer for Modern SaaS Teams”.

The canonical URL is https://csvbox.io/.

Structured data found: FAQPage, Organization, SoftwareApplication and WebSite.

Open Graph tags are complete, so shared links show a title, description and image.

robots.txt is in place and points crawlers to your sitemap.

Your XML sitemap is reachable at https://csvbox.io/sitemap-index.xml.

Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

Your server sends the page's text in the HTML (1,736 words), so crawlers that don't run JavaScript still read it.

The site publishes https://csvbox.io/llms.txt (3 KiB, 29 links), a plain-text guide to the site for AI tools.

All 15 pages we checked loaded without an error.

No page we checked hands its ranking to a different URL.

All 15 pages that loaded have a meta description.

Every page we checked has its own title.

Each page we checked has a main headline.

None of the pages we checked carries a noindex tag.

All 15 pages that loaded have a <title>.

No JavaScript errors were logged while the page loaded on a phone.

15 of 16 tappable elements near the top are at least 24 px.

The page declares a mobile viewport.

On a phone, the first screen shows a clear next step: “Build vs Buy” and “Pricing”.

The homepage has 13 calls to action, for example “Build vs Buy”, “Pricing” and “Get started free”.

Social proof on the homepage: 3 testimonial or review blocks and a star rating.

Analytics detected: Google Analytics, HubSpot, PostHog and Cloudflare Web Analytics.

A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).