Website review, no card needed

pezs.shop logo

pezs.shop website review

Visit site (opens in a new tab)Reviewed 16 November 202631 issues · 74 checks

This review found 31 issues worth fixing on pezs.shop, 10 of them high impact, across 74 checks. The most urgent: render-blocking requests. 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.4 s2.2 sAug 22Sep 122.4 s
Show as table
DateReal-visitor load time (LCP)
Aug 22, 20262.2 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
248 ms235 msAug 22Sep 12244 ms
Show as table
DateReal-visitor tap response (INP)
Aug 22, 2026236 ms
Aug 29, 2026244 ms
Sep 5, 2026246 ms
Sep 12, 2026244 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 pezs.shop (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. pezs.shop at 0.5 s0.5 s
  2. pezs.shop at 1.0 s1.0 s
  3. pezs.shop at 1.5 s1.5 s
  4. pezs.shop at 2.0 s2.0 s
  5. pezs.shop at 2.5 s2.5 s
  6. pezs.shop at 3.0 s3.0 s
  7. pezs.shop at 3.5 s3.5 s
  8. pezs.shop at 4.0 s4.0 s

Speed

4 to fix80
  • Render-blocking requests

    1.2 s

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

  • Improve image delivery

    900 ms · 185 KiB

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

  • Mobile performance score: 80

    80/100

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

  • Reduce unused CSS

    300 ms · 72 KiB

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

  • Use efficient cache lifetimes

    150 ms · 78 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (envato-static.com, Cloudflare and Bing Ads and others), adding 558 KiB and 86 ms of main-thread time.

  • Minify CSS

    12 KiB

    12 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: 0.5 s

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

  • Server response: 450 ms

    450 ms

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

Core Web Vitals

5 to fix79
  • Largest Contentful Paint: 4.5 s

    4.5 s

    Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “STUDIOBET78 | Live Chat Siap Membantu Pengguna Baru”.

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Time to Interactive: 4.6 s

    4.6 s

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

  • Speed Index: 3.6 s

    3.6 s

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

  • 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

    +2%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

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

    0.01

    The layout barely moves while loading (CLS 0.01, 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

1 to fix90
  • 1 image far larger than shown

    44 KiB

    1 image is downloaded at several times the size a phone draws it, for example banner-studiobet78_myegbr.png at 1,080 px wide, shown at 326 px. Resized copies would save about 44 KiB.

  • 1 image in older formats

    1 image (242 KiB) 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.2 g of CO₂ per visit

    0.16 g

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

2 checks passed
  • Page weight: 593 KiB in 26 requests

    593 KiB

    Your homepage downloads 593 KiB in 26 requests on a phone: images 413 KiB (14), stylesheets 77 KiB (3) and scripts 56 KiB (6). That is a lean page.

  • Images load when needed

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

Accessibility

7 to fixGoogle 8388
  • 5 text elements with low contrast

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • <svg> elements with an img or image role must have alternative text (1 element)

    <svg> elements with an img or image role must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (39 elements)

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

  • 3 links without text

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

  • 1 form field without a label

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

1 checks passed
  • 40 automated accessibility rules passed

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

SEO

2 to fixGoogle 8591
  • 3 H1 headlines

    There are 3 <h1> headlines (“STUDIOBET78 | Live Chat Siap Membantu Pengguna Ba…”, “STUDIOBET78 | Live Chat Siap Membantu Pengguna Ba…” and “Live Chat Siap Membantu Pengguna Baru”). One clear main headline is easier for people and search engines.

  • No XML sitemap

    No XML sitemap at https://pezs.shop/sitemap.xml, so Google discovers your pages only by following links.

  • 148 internal links, 49 external

    The homepage links to 148 pages on pezs.shop and 49 external pages.

6 checks passed
  • Meta description: 125 characters

    Your meta description is 125 characters: “STUDIOBET78 menghadirkan Live Chat siap membantu pengguna baru dengan respons cepat, akses mudah, dan layanan yang resp…”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “STUDIOBET78 | Live Chat Siap Membantu Pengguna Baru”.

  • Canonical URL set

    The canonical URL is https://pezs.shop/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and Product.

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

AI search readiness

100
  • No llms.txt

    There is no https://pezs.shop/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: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

3 to fix81
  • 2 pages point its canonical at the homepage

    https://pezs.shop/licenses/standard and https://pezs.shop/item_support/what_is_item_support/8988002 declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 3 pages share a title

    /, https://pezs.shop/licenses/standard and https://pezs.shop/item_support/what_is_item_support/8988002 all use the title “STUDIOBET78 | Live Chat Siap Membantu Pengguna Baru”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://pezs.shop/licenses/standard and https://pezs.shop/item_support/what_is_item_support/8988002 use the same meta description. A description written for each page earns more clicks.

  • 2 internal pages checked

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

5 checks passed
  • Linked pages load

    All 2 pages we checked loaded without an error.

  • Every page has a meta description

    All 2 pages 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 2 pages that loaded have a <title>.

Best practices

5 to fixGoogle 6969
  • 1 broken image

    1 image failed to load on a phone, for example https://ik.imagekit.io/hkscvu9il/daftar-login.gif?updatedAt=1771893609804.

  • 11 small tap targets

    11 of 30 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.”).

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Error: <svg> attribute viewBox: Unexpected end of attribute. Expected number, "0 0 1414".”.

  • 1 distorted image

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • No call to action on the first screen

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

  • 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 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 405 words of copy

    The homepage carries about 405 words of visible text.

3 checks passed
  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 11 testimonial or review blocks, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Microsoft Ads (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.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie, 1 of them by other companies (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.

  • 9 other companies contacted

    Loading the homepage contacts 9 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 pezs.shop, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Plus
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on pezs.shop, including 9 speed issues, 2 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