routerabbit.com website review

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

About 1.3 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 7.5 s faster on a phone.

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

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

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

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

6 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.0 MB and 560 ms of main-thread time.

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

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

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

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

5 KiB could be saved by minifying CSS.

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

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

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

Your largest element takes 27.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (14.0 s).

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.7 MB in 137 requests on a phone: scripts 2.0 MB (89), stylesheets 1.4 MB (7) and images 618 KiB (25). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example Kubernetes-e1675160707343-297x300.png at 297 px wide, shown at 70 px. Resized copies would save about 51 KiB.

4 images (179 KiB) are 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.

5 images further down the page (203 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 1.33 g of CO₂e: 159.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There are 4 <h1> headlines (“Earned the trust of”, “Our Technology Stack” and “Our simple process produces results fast”). One clear main headline is easier for people and search engines.

No XML sitemap at https://routerabbit.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at routerabbit.com/robots.txt, the first file search crawlers ask for.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 34 pages on routerabbit.com and 1 external page.

There is no https://routerabbit.com/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.

Your homepage links to https://routerabbit.com/get-a-proposal, https://routerabbit.com/services, https://routerabbit.com/products and https://routerabbit.com/clients, which answer with an error. Visitors hit a dead end and search engines drop them.

https://routerabbit.com/blog/solutions/saas-application-development has no meta description, so Google writes the search snippet from whatever text it finds.

https://routerabbit.com/about-us and https://routerabbit.com/blog/solutions/saas-application-development took over 3 s to send their HTML from our server.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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

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