stonerosesstore.com website review

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

4 images could be 4.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 22.9 s faster on a phone.

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

Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.

About 186 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 740 ms faster on a phone.

6 third-party services load with your homepage (teepublic.com, Google Analytics and Cloudflare and others), adding 5.2 MB and 345 ms of main-thread time.

wlsf.link costs a phone 0 ms of main-thread work and 4.6 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.

teepublic.com costs a phone 155 ms of main-thread work and 393 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 1,726 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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.

3 KiB could be saved by minifying JavaScript.

Your largest element takes 28.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “TOPANHOKI - Portal Data Toto Macau 2026 dengan Result dan K…”.

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

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

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

5 images 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.

2 images weigh 4.5 MB together. On a phone connection a single image that size takes seconds.

Your homepage downloads 5.3 MB in 40 requests on a phone: images 4.6 MB (21), scripts 380 KiB (11) and fonts 142 KiB (4). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example josjis.png at 1,254 px wide, shown at 390 px. Resized copies would save about 906 KiB.

2 images (4.5 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.

By the Sustainable Web Design model, a visit to your homepage emits about 1.50 g of CO₂e: 179.5 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”.

3 links inside paragraphs rely on colour alone to stand out.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

1 element has a tabindex above 0, which scrambles the keyboard order.

42 images have no alt text, which hurts accessibility and image search.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 80 characters, so Google will cut it off around 60: “TOPANHOKI - Portal Data Toto Macau 2026 dengan Result dan Keluaran Angka Terkini”.

There are 2 <h1> headlines (“TOPANHOKI : Menyediakan Result Sah Data Toto Maca…” and “TOPANHOKI - Portal Data Toto Macau 2026 dengan Re…”). One clear main headline is easier for people and search engines.

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

7 links have no real href, so search engines can't follow them.

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

The homepage links to 132 pages on stonerosesstore.com and 17 external pages.

The robots meta tag says “index, follow, nosnippet”, which tells Google, Bing and the AI answers built on them not to quote this page.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

Your homepage links to https://stonerosesstore.com/t-shirts, https://stonerosesstore.com/privacy_policy, https://stonerosesstore.com/order/status, https://stonerosesstore.com/contact, https://stonerosesstore.com/shipping and https://stonerosesstore.com/sizechart and 8 others, which answer with an error. Visitors hit a dead end and search engines drop them.

https://stonerosesstore.com/products/tsr-logo-hoody-black declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://stonerosesstore.com/products/tsr-logo-hoody-black all use the title “TOPANHOKI - Portal Data Toto Macau 2026 dengan Result dan Keluaran An…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://stonerosesstore.com/products/tsr-logo-hoody-black has no <h1> headline, so visitors and search engines get no clear main topic.

https://stonerosesstore.com/products/tsr-logo-hoody-black has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

6 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot set properties of null (setting 'innerHTML')”.

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

Before a visitor clicks anything, the page loads Google Analytics (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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