Website review, no card needed

mysterypokeslabs.com logo

mysterypokeslabs.com website review

Visit site (opens in a new tab)Reviewed 20 November 202636 issues · 86 checks

This review found 36 issues worth fixing on mysterypokeslabs.com, 11 of them high impact, across 86 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

Real-visitor load time (LCP)75th percentile, phones
2.1 s1.6 sMay 30Nov 141.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.0 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20261.9 s
Oct 17, 20261.8 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Nov 7, 20261.7 s
Nov 14, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
88 ms78 msMay 30Nov 1485 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202679 ms
Jun 6, 202679 ms
Jun 13, 202681 ms
Jun 20, 202683 ms
Jun 27, 202686 ms
Jul 4, 202686 ms
Jul 11, 202685 ms
Jul 18, 202682 ms
Jul 25, 202681 ms
Aug 1, 202680 ms
Aug 8, 202685 ms
Aug 15, 202687 ms
Aug 22, 202687 ms
Aug 29, 202687 ms
Sep 5, 202686 ms
Sep 12, 202684 ms
Sep 19, 202685 ms
Sep 26, 202685 ms
Oct 3, 202683 ms
Oct 10, 202686 ms
Oct 17, 202686 ms
Oct 24, 202687 ms
Oct 31, 202687 ms
Nov 7, 202686 ms
Nov 14, 202685 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of mysterypokeslabs.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mysterypokeslabs.com at 4.4 s4.4 s
  2. mysterypokeslabs.com at 8.8 s8.8 s
  3. mysterypokeslabs.com at 13.1 s13.1 s
  4. mysterypokeslabs.com at 17.5 s17.5 s
  5. mysterypokeslabs.com at 21.9 s21.9 s
  6. mysterypokeslabs.com at 26.3 s26.3 s
  7. mysterypokeslabs.com at 30.6 s30.6 s
  8. mysterypokeslabs.com at 35.0 s35.0 s

Speed

12 to fix40
  • Improve image delivery

    1.1 s · 1.4 MB

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

  • Main-thread work: 16.9 s

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

  • Mobile performance score: 40

    40/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Facebook and Google Tag Manager and others), adding 1.2 MB and 2.6 s of main-thread time.

  • 20 long tasks on the main thread

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

  • Klaviyo adds 606 ms

    606 ms

    Klaviyo costs a phone 606 ms of main-thread work and 318 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.

  • Facebook adds 512 ms

    512 ms

    Facebook costs a phone 512 ms of main-thread work and 222 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.

  • Google Tag Manager adds 488 ms

    488 ms

    Google Tag Manager costs a phone 488 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.

  • aimerce.ai adds 418 ms

    418 ms

    aimerce.ai costs a phone 418 ms of main-thread work and 106 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.

  • Reduce unused JavaScript

    356 KiB

    About 356 KiB of JavaScript is downloaded but never used on this page.

  • Shopify adds 327 ms

    327 ms

    Shopify costs a phone 327 ms of main-thread work and 258 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.

  • Render-blocking requests

    350 ms

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

  • Use efficient cache lifetimes

    210 KiB

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

  • Font display

    100 ms

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

  • Legacy JavaScript

    37 KiB

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

  • Reduce unused CSS

    16 KiB

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

  • 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 12 ms

    12 ms

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

Core Web Vitals

7 to fix100
  • Fails Core Web Vitals for real visitors

    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.

  • Speed Index: 14.1 s

    14.1 s

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

  • Time to Interactive: 21.5 s

    21.5 s

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

  • Total Blocking Time: 2.0 s

    2.0 s

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

  • Largest Contentful Paint: 6.0 s

    6.0 s

    Your largest element takes 6.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mystery Poke Slabs giveaway: BBG28: $60,000 or 1999 Pokémon…”.

  • Real-user TTFB: 969 ms

    969 ms

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 79 ms to 85 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

7 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 78 ms

    78 ms

    Real visitors wait 78 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.6 s

    1.6 s

    Real visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.

  • Largest content (LCP) got 15% faster for real visitors

    -15%

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

  • First Contentful Paint: 1.3 s

    1.3 s

    The first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix42
  • Page weight: 5.8 MB in 408 requests

    5.8 MB

    Your homepage downloads 5.8 MB in 408 requests on a phone: images 2.9 MB (44), other files 1.4 MB (263) and scripts 1.1 MB (73). Under 2 MB keeps phones on slow connections fast.

  • 22 images in older formats

    22 images (2.0 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.

  • An image on the first screen is lazy-loaded

    lander_and_checkout_button_sticker_-_oct_27_2026.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image far larger than shown

    180 KiB

    1 image is downloaded at several times the size a phone draws it, for example lander_and_checkout_button_sticker_-_oct_27_2026.webp at 1,844 px wide, shown at 278 px. Resized copies would save about 180 KiB.

  • About 1.6 g of CO₂ per visit

    1.64 g

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

Accessibility

4 to fixGoogle 10095
  • 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 (4 elements)

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

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

  • Headings skip levels

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

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

3 to fixGoogle 10083
  • Title is long (82 characters)

    Your title is 82 characters, so Google will cut it off around 60: “Mystery Pokemon Slabs | Only Official Website & Daily Giveaways – MysteryPokeSlabs”.

  • Meta description is long (313 characters)

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

  • One H1 headline

    Your <h1> is empty.

  • 64 internal links, 4 external

    The homepage links to 64 pages on mysterypokeslabs.com and 4 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://mysterypokeslabs.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

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

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://mysterypokeslabs.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

Other pages

1 to fix95
  • 1 page without an H1

    https://mysterypokeslabs.com/pages/sealed-pokemon has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    1 page of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 1 page that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    24 of 28 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix78
  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 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.

  • About 1,453 words of copy

    The homepage carries about 1,453 words of visible text.

  • Urgency cues

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Now”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 91 testimonial or review blocks, a star rating and 6 trust badges.

  • Analytics in place

    Analytics detected: Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.

  • 22 cookies set on arrival

    22

    Opening the homepage sets 22 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.

  • 27 other companies contacted

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

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 mysterypokeslabs.com, 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 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Triplewhale · Aimerce First Party Pixel · Klaviyo Email Marketing Sms · rechargecdn.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
Tailwind CSS
E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on mysterypokeslabs.com, including 19 speed issues, 3 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