weareupspring.com website review

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

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

Your mobile performance score is 40 (desktop: 64). 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, website-files.com and Facebook and others), adding 3.8 MB and 1.6 s of main-thread time.

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

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

Google Tag Manager costs a phone 692 ms of main-thread work and 1.0 MB 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 424 ms of main-thread work and 2.3 MB 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.6 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

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.

Your largest element takes 13.5 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 6.0 s on a phone. Good is under 1.8 s.

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

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

Scripts block taps and scrolling for 672 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.0 MB in 91 requests on a phone: images 1.8 MB (20), scripts 1.6 MB (35) and fonts 363 KiB (7). Under 2 MB keeps phones on slow connections fast.

6ab6236e45b7098f57f62db4_3877-p-500.webp 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).

3 images are downloaded at several times the size a phone draws them, for example 6ab6209b611a8be5eef242bf_jcj_14aa6e2a14a1d1f847a7fece14ef072 at 1,692 px wide, shown at 350 px. Resized copies would save about 236 KiB.

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

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

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

Structured data found (FAQPage, Organization and ProfessionalService) but with 1 problem, for example “ProfessionalService: sameAs is not an absolute URL ("https://observer.com/[CONFIRM: Top interior de…”.

The homepage links to 50 pages on weareupspring.com and 4 external pages.

We fetched 15 pages linked from your homepage (of 24 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”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

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

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

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