rumpl.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, rebuyengine.com and Clarity and others), adding 1.6 MB and 1.2 s of main-thread time.

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

About 832 KiB of JavaScript is downloaded but never used on this page.

The page goes through 1 redirect before it starts loading, costing about 751 ms. Link and advertise the final URL directly.

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

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

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

rebuyengine.com costs a phone 167 ms of main-thread work and 332 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.

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

The HTML itself could arrive about 150 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

28 KiB JavaScript is shipped twice across bundles.

About 18 KiB of CSS is downloaded but never applied on this page.

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.

2 KiB could be saved by minifying CSS.

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 page becomes fully interactive after 23.5 s. Good is under 3.8 s.

Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “There’s An Art To Gifting”.

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

Scripts block taps and scrolling for 653 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.

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

Your homepage downloads 11.9 MB in 432 requests on a phone: media 6.5 MB (5), scripts 2.2 MB (121) and images 1.9 MB (37). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example CategoryHighlight_Mats.jpg at 600 px wide, shown at 171 px. Resized copies would save about 113 KiB.

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

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

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.

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

1 element hidden from screen readers can still receive keyboard focus.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 28 characters: “Verifying your connection...”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

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

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17415968&Ver=2&mid=3a3f90e6-becc-45e8-82b8-318ae43878a7&bo=1&sid=0b1f5640d8a411f1be6b85353888c70c&vid=0b1fc7f0d8a411f1975b696e072cdf49&vids=1&msclkid=N&pi=918639831&lg.

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 “Failed to load resource: net::ERR_FAILED”.

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

Your homepage answered with HTTP 429, so visitors and search engines may see an error page.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 5 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 47 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 57 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.