stayaka.com website review

About 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.4 s faster on a phone.

94 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).

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

Google Tag Manager costs a phone 1.4 s of main-thread work and 1.4 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Google Tag Manager, cloudflarestream.com and Google CDN and others), adding 4.0 MB and 3.7 s of main-thread time.

cloudflarestream.com costs a phone 839 ms of main-thread work and 737 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.

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

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

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

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

triptease.io costs a phone 293 ms of main-thread work and 165 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.

gethovr.com costs a phone 244 ms of main-thread work and 343 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 78 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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.

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

Your largest element takes 24.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Mute/Unmute”.

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

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

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

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

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

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-24, real Chrome visitors' tap response (inp) went from 136 ms to 157 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 6.8 MB in 260 requests on a phone: scripts 4.7 MB (116), images 1.1 MB (24) and other files 471 KiB (86). Under 2 MB keeps phones on slow connections fast.

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

1 dropdown has no label.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 107 pages on stayaka.com and 4 external pages.

There is no https://www.stayaka.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.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=23002112&tm=gtm002&Ver=2&mid=09b279b8-86e5-4d1b-a2b3-b282b5c99e93&bo=2&sid=d42f6e30d45511f19bd13ba6bef1ec49&vid=d42fbb80d45511f1b5e9736ad077c06e&vids=1&msclkid=N&pi=91.

5 errors were logged to the browser console while the page loaded, for example “Error processing event queue Unsupported tag command "s"”.

Large scripts ship without source maps.

Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 6 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 20 cookies, 1 of them by other companies (measured from a US location before any click).

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