michaelscookies.com website review

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

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

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

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

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

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

5 third-party services load with your homepage (samsung.com, Google Maps and Cloudflare and others), adding 1.8 MB and 1.0 s of main-thread time.

13 long tasks block the main thread while loading, the longest for 1.1 s. During a long task the page ignores taps.

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

samsung.com costs a phone 854 ms of main-thread work and 1.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.

2 images could be 140 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

Google Maps costs a phone 152 ms of main-thread work and 328 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 16 KiB JavaScript that modern phones do not need.

Desktop scores 63 but mobile only 34. A gap that wide usually means heavy scripts and images that hit phones hardest.

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 11.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Popup Banner”.

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

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

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

The first text or image appears after 3.2 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.

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.

1 image is downloaded at several times the size a phone draws it, for example 33.webp at 1,080 px wide, shown at 338 px. Resized copies would save about 23 KiB.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

Elements with visible text labels do not have matching accessible names. (3 elements).

Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

There are 2 <h1> headlines (“Situs Bonus Slot: Bonus New Member 100 & Slot Gac…” and “Situs Bonus Slot: Bonus New Member 100 & Slot Gac…”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 87 pages on michaelscookies.com and 47 external pages.

Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

Your homepage links to https://www.piwispizza.com/kebijakan-privasi, https://www.piwispizza.com/legal and https://www.piwispizza.com/sitemap, which answer with an error. Visitors hit a dead end and search engines drop them.

We fetched 3 pages linked from your homepage and read each the way a search engine does.

1 image failed to load on a phone, for example https://www.piwispizza.com/items/jalapeno-poppers#.

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

3 errors were logged to the browser console while the page loaded, for example “Unsafe attempt to load URL https://www.samsung.com/etc.clientlibs/samsung/clientlibs/consumer/global/clientlib-common/r…”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 139 words of visible text; thin pages give Google and first-time buyers little to go on.

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.