recro.io website review

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

framerusercontent.com costs a phone 3.8 s of main-thread work and 1.6 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 824 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

Hotjar costs a phone 1.9 s of main-thread work and 71 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

8 third-party services load with your homepage (framerusercontent.com, Hotjar and Google Tag Manager and others), adding 2.7 MB and 7.0 s of main-thread time.

Google Tag Manager costs a phone 689 ms of main-thread work and 779 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 482 ms. During a long task the page ignores taps.

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

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

The page has 1,572 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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.

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

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

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

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

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

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

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

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

Your homepage downloads 2.9 MB in 178 requests on a phone: scripts 1.9 MB (66), images 838 KiB (50) and other files 97 KiB (57). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example YRDTp333Wh0vi7nUaDz7b6u1Q.png at 2,000 px wide, shown at 282 px. Resized copies would save about 366 KiB.

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

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

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

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

The homepage links to 59 pages on recro.io and 4 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.recro.io/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.recro.io/case-study, https://www.recro.io/about, https://www.recro.io/community, https://www.recro.io/ai-llm-acceleration and https://www.recro.io/contact and 7 others all use the title “Recro: Developer-First Platform for the Right Opportunities”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.recro.io/case-study, https://www.recro.io/about, https://www.recro.io/community, https://www.recro.io/ai-llm-acceleration, https://www.recro.io/contact and https://www.recro.io/partnerships and 6 others use the same meta description. A description written for each page earns more clicks.

https://www.recro.io/about has no <h1> headline, so visitors and search engines get no clear main topic.

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

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

The homepage carries about 538 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight and 2 mores (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 13 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 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.