onedge.co website review

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

About 418 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.

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

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

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

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

16 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

Amazon Web Services costs a phone 0 ms of main-thread work and 701 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 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

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

Desktop scores 77 but mobile only 35. 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 4.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Your largest element takes 18.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Book a Demo”.

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

Visually, the page fills in at 9.8 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 336 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 206 ms to 327 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

20 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 3.9 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.1 MB in 141 requests on a phone: images 1.4 MB (22), scripts 1.4 MB (33) and fonts 1.0 MB (3). Under 2 MB keeps phones on slow connections fast.

9 images (1.3 MB) 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.

3 images are downloaded at several times the size a phone draws them, for example AngeloC.jpg at 1,254 px wide, shown at 358 px. Resized copies would save about 173 KiB.

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

4 dropdowns have no label.

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

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

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

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

The homepage links to 137 pages on onedge.co and 11 external pages.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 1,320 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel 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 11 cookies (measured from a US location before any click).

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