hiro.so website review

About 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.6 s faster on a phone.

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

Your mobile performance score is 36 (desktop: 44). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

Google CDN costs a phone 756 ms of main-thread work and 1.8 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.

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

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

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

Digioh costs a phone 176 ms of main-thread work and 409 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.

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

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

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

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

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

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.

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

Your largest element takes 28.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “BITCOIN”.

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

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

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

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

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

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

Your homepage downloads 5.2 MB in 109 requests on a phone: scripts 3.4 MB (54), other files 708 KiB (16) and images 354 KiB (19). Under 2 MB keeps phones on slow connections fast.

1 image (63 KiB) is 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 1.46 g of CO₂e: 175.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your meta description is only 67 characters: “Building on Bitcoin is hard. Hiro’s developer tools make it easier.”. 70 to 160 characters is enough to sell the click.

There are 3 <h1> headlines (“BUILD WEB3ON BITCOIN.”, “BUILD ON BITCOIN LAYERS.” and “BUILD WEB3ON BITCOIN.”). One clear main headline is easier for people and search engines.

The homepage links to 43 pages on hiro.so and 22 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.

/ordhook has no <title>, so Google invents the link text in results.

/ordhook has no meta description, so Google writes the search snippet from whatever text it finds.

/ordhook and /updates have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 21 found) 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.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Framing 'https://www.google.com/' violates the following report-only Content Security Policy directive: "frame-ancestor…”.

3 links to other sites are dead, for example https://docs.hiro.so/guides (404).

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

3 links go through two or more redirects, for example https://www.hiro.so/ordhook.

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.

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.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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 Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Segment and 1 more (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 8 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 29 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.