getblys.com website review

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

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

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

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

Your mobile performance score is 63 (desktop: 73). Pages that score under 90 lose visitors before the first paint.

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

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

8 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and New Relic and others), adding 843 KiB and 228 ms of main-thread time.

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

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

Polyfills for old browsers add 17 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.

3 KiB could be saved by minifying CSS.

2 KiB could be saved by minifying JavaScript.

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 2.3 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 11.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to enhance your browsing experience, analyse…”. Most of its time is element render delay (8.2 s).

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

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

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

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

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

1 image have no width and height attributes, so the layout jumps as each one loads.

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 17.3 MB in 84 requests on a phone: images 14.6 MB (33), scripts 1.4 MB (18) and fonts 796 KiB (7). Under 2 MB keeps phones on slow connections fast.

9 images weigh 13.2 MB together. On a phone connection a single image that size takes seconds.

10 images are downloaded at several times the size a phone draws them, for example image-1730663175745.jpeg at 2,316 px wide, shown at 48 px. Resized copies would save about 7.4 MB.

20 images (14.2 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.

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

1 button has no accessible name, so screen readers announce just “button”.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Structured data found (FAQPage, Organization, Service and VideoObject) but with 1 problem, for example “Service: no offers (price) block”.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 271 pages on getblys.com and 65 external pages.

/us/services/massage, /us/services/swedish, /us/services/deep-tissue-massage, /us/services/couples-massage, /us/services/prenatal-massage and /us/services/postnatal-massage and 3 others took over 3 s to send their HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-livechat.getblys.com/prod/bundle/blys-chat-wp.css' from origin 'https://getbly…”.

Large scripts ship without source maps.

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.

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

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

The homepage carries about 3,161 words of visible text.

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