rapdev.io website review

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

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

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

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

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

8 third-party services load with your homepage (JSDelivr CDN, Google Tag Manager and Hubspot and others), adding 1.5 MB and 1.9 s of main-thread time.

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

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

JSDelivr CDN costs a phone 878 ms of main-thread work and 426 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.

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

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

Hubspot costs a phone 261 ms of main-thread work and 136 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 115 ms of main-thread work and 466 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.

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

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

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

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.

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

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

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

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

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

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

12 images have no width and height attributes, so the layout jumps as each one loads.

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

1 image further down the page (24 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

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

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

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Structured data found (Organization) but with 1 problem, for example “Organization: url is not an absolute URL ("/")”.

12 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 341 pages on rapdev.io and 16 external pages.

There is no https://www.rapdev.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.

We fetched 15 pages linked from your homepage (of 134 found) and read each the way a search engine does.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Error: <svg> attribute height: Expected length, "auto".”.

Chrome logged issues while loading the page (“Cookie”).

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 7 cookies (measured from a US location before any click).

Loading the homepage contacts 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.