moonlightbrand.sk website review

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

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

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

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

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

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

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

Google Fonts costs a phone 1 ms of main-thread work and 339 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.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

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

2 third-party services load with your homepage (Google Fonts and gorgias.chat), adding 341 KiB and 1 ms of main-thread time.

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.

1 file is served with short cache lifetimes, so returning visitors download them again (3 KiB).

Your largest element takes 12.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is element render delay (8.7 s).

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

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

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

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

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

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 2.4 MB in 90 requests on a phone: images 1.1 MB (43), scripts 670 KiB (25) and fonts 337 KiB (7). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example moonlight-logo-transparent.png at 913 px wide, shown at 56 px. Resized copies would save about 61 KiB.

3 images (131 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 0.67 g of CO₂e: 80.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

Structured data found (Organization, SoftwareApplication, WebPage and WebSite) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.

The homepage links to 39 pages on moonlightbrand.sk and 5 external pages.

https://moonlightscan.com/api/sleep-freely/manage has no <title>, so Google invents the link text in results.

https://moonlightscan.com/scan, https://moonlightscan.com/cycle, https://moonlightscan.com/api/sleep-freely/manage, https://moonlightscan.com/reviews, https://moonlightscan.com/story and https://moonlightscan.com/business and 2 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/, https://moonlightscan.com/scan, https://moonlightscan.com/cycle and https://moonlightscan.com/business all use the title “moonScan - Camera-Based Recovery Intelligence”. Search engines can't tell which page to show for a search, so each competes with the others.

https://moonlightscan.com/api/sleep-freely/manage has no meta description, so Google writes the search snippet from whatever text it finds.

https://moonlightscan.com/scan, https://moonlightscan.com/cycle and https://moonlightscan.com/business use the same meta description. A description written for each page earns more clicks.

https://moonlightscan.com/scan, https://moonlightscan.com/cycle, https://moonlightscan.com/api/sleep-freely/manage, https://moonlightscan.com/reviews, https://moonlightscan.com/story and https://moonlightscan.com/business and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

Large scripts ship without source maps.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage carries about 2,617 words of visible text.

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