onerpm.com website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 1.3 MB and 1.6 s of main-thread time.

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

98 KiB could be saved by minifying JavaScript.

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

Facebook costs a phone 425 ms of main-thread work and 311 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.

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

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

2 images could be 42 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.

20 KiB could be saved by minifying CSS.

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

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

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

Desktop scores 54 but mobile only 11. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

Real visitors wait 5.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.92 (75th percentile). Good is under 0.1.

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

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

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

The layout shifts by 0.927 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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

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

2 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-24, real Chrome visitors' largest content (lcp) went from 4.8 s to 4.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.5 MB in 147 requests on a phone: images 2.5 MB (35), scripts 1.6 MB (41) and HTML 189 KiB (1). Under 2 MB keeps phones on slow connections fast.

CO-La-Banda-del-5_mobile.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example img_OurApproach-scaled-2.webp at 2,560 px wide, shown at 390 px. Resized copies would save about 191 KiB.

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

9 images (446 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.

By the Sustainable Web Design model, a visit to your homepage emits about 1.27 g of CO₂e: 152.8 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.

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

16 images have no alt text, which hurts accessibility and image search.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your hreflang tags are invalid, so Google may show the wrong language version.

The homepage links to 97 pages on onerpm.com and 58 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://onerpm.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.

https://onerpm.com/onepublishing, https://onerpm.com/our-locations, https://onerpm.com/onerpmgospel, https://onerpm.com/press-releases, https://onerpm.com/terms-of-use and https://onerpm.com/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://onerpm.com/onepublishing has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

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

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