Website review, no card needed

oliver-michallik.de logo

oliver-michallik.de website review

Visit site (opens in a new tab)Reviewed 18 November 202645 issues · 91 checks

This review found 45 issues worth fixing on oliver-michallik.de, 18 of them high impact, across 91 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of oliver-michallik.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. oliver-michallik.de at 0.5 s0.5 s
  2. oliver-michallik.de at 1.1 s1.1 s
  3. oliver-michallik.de at 1.6 s1.6 s
  4. oliver-michallik.de at 2.2 s2.2 s
  5. oliver-michallik.de at 2.7 s2.7 s
  6. oliver-michallik.de at 3.3 s3.3 s
  7. oliver-michallik.de at 3.8 s3.8 s
  8. oliver-michallik.de at 4.3 s4.3 s

Speed

7 to fix63
  • Improve image delivery

    6.6 s · 1.5 MB

    1 image could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.6 s faster on a phone.

  • Render-blocking requests

    1.2 s

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

  • Reduce unused JavaScript

    900 ms · 178 KiB

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

  • Mobile performance score: 63

    63/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (seabrafoods.com, Shopify and Cloudflare and others), adding 2.3 MB and 439 ms of main-thread time.

  • seabrafoods.com adds 362 ms

    362 ms

    seabrafoods.com costs a phone 362 ms of main-thread work and 534 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.

  • postimg.cc adds 0 ms

    0 ms

    postimg.cc costs a phone 0 ms of main-thread work and 1.5 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.

  • Use efficient cache lifetimes

    200 ms · 197 KiB

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

  • Reduce unused CSS

    180 ms · 95 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    21 KiB

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

  • Minify JavaScript

    17 KiB

    17 KiB could be saved by minifying JavaScript.

  • Minify CSS

    14 KiB

    14 KiB could be saved by minifying CSS.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 checks passed
  • Main-thread work: 1.9 s

    A phone's processor spends 1.9 s on main-thread work while loading, 564 ms of it running JavaScript. That is comfortably low.

  • Server response: 434 ms

    434 ms

    Your server sent the HTML in 434 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix67
  • Largest Contentful Paint: 14.5 s

    14.5 s

    Your largest element takes 14.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “RATU89 | Strategi rahasia mencapai slot maxwin dengan memil…”.

  • Time to Interactive: 14.5 s

    14.5 s

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

  • Speed Index: 8.8 s

    8.8 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • 2 images without width and height

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

  • Not enough real-visitor data yet

    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 checks passed
  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix60
  • 1 image over 500 KB

    8a98e10a50ba4ad392295a20062b21a4.png weighs 1.5 MB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.1 MB in 92 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 92 requests on a phone: images 1.6 MB (4), scripts 778 KiB (38) and other files 458 KiB (40). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (1.5 MB) is 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.

  • About 0.9 g of CO₂ per visit

    0.89 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

12 to fixGoogle 6584
  • Certain ARIA roles must contain particular children (2 elements)

    Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 1 button without a name

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

  • Hidden but focusable

    5 elements hidden from screen readers can still receive keyboard focus.

  • 3 text elements with low contrast

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

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 7 links without text

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

  • 6 form fields without a label

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

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 64 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 13 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 6769
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is long (97 characters)

    Your title is 97 characters, so Google will cut it off around 60: “RATU89 | Strategi rahasia mencapai slot maxwin dengan memilih permainan berdasarkan data …”.

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, FAQPage, Product and ProductGroup) but with 1 problem, for example “Product: no offers (price) block”.

  • No XML sitemap

    No XML sitemap at https://oliver-michallik.de/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at oliver-michallik.de/robots.txt, the first file search crawlers ask for.

  • 4 links crawlers can't follow

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 149 internal links, 7 external

    The homepage links to 149 pages on oliver-michallik.de and 7 external pages.

3 checks passed
  • One H1 headline

    Your main headline reads: “RATU89 | Strategi rahasia mencapai slot maxwin dengan memilih permainan berdasarkan data RTP live Sale”.

  • Canonical URL set

    The canonical URL is https://oliver-michallik.de/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://oliver-michallik.de/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.

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (984 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix58
  • 14 linked pages are broken

    Your homepage links to https://oliver-michallik.de/collections/beef/products/beef-short-rib-sliced-4pc-1lb, https://oliver-michallik.de/pages/privacy-policy-politica-de-privacidade, https://oliver-michallik.de/collections/grocery, https://oliver-michallik.de/collections/produce-horti-frut, https://oliver-michallik.de/collections/fresh-salad and https://oliver-michallik.de/collections/fruit and 8 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 page points its canonical at the homepage

    https://oliver-michallik.de/amp/RATU89.html 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.

  • 2 pages share a title

    / and https://oliver-michallik.de/amp/RATU89.html all use the title “RATU89 | Strategi rahasia mencapai slot maxwin dengan memilih permain…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page with very little text

    https://oliver-michallik.de/amp/RATU89.html 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.

  • 15 internal pages checked

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

4 checks passed
  • Every page has a meta description

    All 1 page that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 1 page that loaded have a <title>.

Best practices

4 to fixGoogle 7370
  • 1 broken image

    1 image failed to load on a phone, for example https://oliver-michallik.de/#.

  • 18 small tap targets

    18 of 36 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • Local business without LocalBusiness data

    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.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No direct contact details

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

  • No opening hours

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

  • No map or directions link

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 547 words of copy

    The homepage carries about 547 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Subscribe”, “Learn More” and “Register”.

  • 5 short forms

    5 short forms (3 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 2 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 14 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at oliver-michallik.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Avada Seo Suite · Stape Conversion Tracking · Promotion Popup Allnew · Stape Remix · chimpstatic.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
React
E-commerce
Shopify
Hosting
DigitalOcean

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on oliver-michallik.de, including 12 speed issues, 7 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25
oliver-michallik.de website review: scores and fixes