Website review, no card needed
pepperfield.cz website review
Visit site (opens in a new tab)Reviewed 7 November 202641 issues · 88 checks
This review found 41 issues worth fixing on pepperfield.cz, 20 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
76C- #66,366 of 108,197 reviewed websitesbeats 34%
- #42,605 of 61,318 online storesbeats 26%
- #40,442 of 55,951 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 200 ms |
| May 23, 2026 | 223 ms |
| May 30, 2026 | 218 ms |
| Jun 6, 2026 | 230 ms |
| Jun 13, 2026 | 225 ms |
| Jun 20, 2026 | 231 ms |
| Jun 27, 2026 | 223 ms |
| Jul 4, 2026 | 229 ms |
| Jul 11, 2026 | 232 ms |
| Jul 18, 2026 | 223 ms |
| Jul 25, 2026 | 229 ms |
| Aug 1, 2026 | 217 ms |
| Aug 8, 2026 | 228 ms |
| Aug 15, 2026 | 230 ms |
| Aug 22, 2026 | 227 ms |
| Aug 29, 2026 | 231 ms |
| Sep 5, 2026 | 218 ms |
| Sep 12, 2026 | 211 ms |
| Sep 19, 2026 | 206 ms |
| Sep 26, 2026 | 179 ms |
| Oct 3, 2026 | 182 ms |
| Oct 10, 2026 | 186 ms |
| Oct 17, 2026 | 186 ms |
| Oct 24, 2026 | 186 ms |
| Oct 31, 2026 | 187 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
Speed
Reduce unused JavaScript
3.7 s · 977 KiBAbout 977 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.7 s faster on a phone.
Use efficient cache lifetimes
2.5 s · 679 KiB15 files are served with short cache lifetimes, so returning visitors download them again (679 KiB).
Main-thread work: 29.0 s
A phone's processor spends 29.0 s on main-thread work while loading, 13.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
ContentSquare adds 1.3 s
1.3 sContentSquare costs a phone 1.3 s of main-thread work and 215 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 39
39/100Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5,014 HTML elements
The page has 5,014 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (ContentSquare, appstle.com and Clarity and others), adding 2.3 MB and 4.4 s of main-thread time.
Improve image delivery
650 ms · 661 KiB18 images could be 661 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.
appstle.com adds 977 ms
977 msappstle.com costs a phone 977 ms of main-thread work and 88 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.
Clarity adds 795 ms
795 msClarity costs a phone 795 ms of main-thread work and 29 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
650 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
stape.net adds 541 ms
541 msstape.net costs a phone 541 ms of main-thread work and 324 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 CSS
330 ms · 61 KiBAbout 61 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 330 ms faster on a phone.
Shopify adds 296 ms
296 msShopify costs a phone 296 ms of main-thread work and 751 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 323 ms. During a long task the page ignores taps.
Legacy JavaScript
50 ms · 17 KiBPolyfills for old browsers add 17 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
Minify JavaScript
30 ms · 18 KiB18 KiB could be saved by minifying JavaScript.
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: 25 ms
25 msYour server sent the HTML in 25 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 23.0 s
23.0 sYour largest element takes 23.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Aby náš e-shop správně fungoval a nákupy byly co nejlepší, …”.
Time to Interactive: 28.7 s
28.7 sThe page becomes fully interactive after 28.7 s. Good is under 3.8 s.
Speed Index: 11.6 s
11.6 sVisually, the page fills in at 11.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.4 s
1.4 sScripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.
10 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 167 ms
167 msReal visitors wait 167 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 512 ms
512 msReal visitors wait 512 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 200 ms to 187 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 5.5 MB in 415 requests
5.5 MBYour homepage downloads 5.5 MB in 415 requests on a phone: scripts 2.3 MB (148), other files 1.4 MB (193) and images 1.3 MB (54). Under 2 MB keeps phones on slow connections fast.
4 images far larger than shown
31 KiB4 images are downloaded at several times the size a phone draws them, for example r50.jpg at 520 px wide, shown at 167 px. Resized copies would save about 31 KiB.
5 images below the first screen load straight away
5 images further down the page (300 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.6 g of CO₂ per visit
1.56 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.56 g of CO₂e: 186.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
8 buttons without a name
8 buttons have no accessible name, so screen readers announce just “button”.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
11 images without alt text
11 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
21 links without text
21 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (2 elements)
Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 9 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No page title
Your page has no <title>, so Google has to invent the blue link in search results.
15 links crawlers can't follow
15 links have no real href, so search engines can't follow them.
275 internal links, 6 external
The homepage links to 275 pages on pepperfield.cz and 6 external pages.
7 checks passed
Meta description: 91 characters
Your meta description is 91 characters: “Jsme opravdoví, Kampotský pepř milujeme a budeme rádi, když nám napíšete, jak vám chutnalo.”.
One H1 headline
Your main headline reads: “.pepper..field®”.
Canonical URL set
The canonical URL is https://pepperfield.cz/.
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://pepperfield.cz/sitemap.xml.
AI search readiness
4 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 (1,183 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://pepperfield.cz/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
14 pages without a title
https://pepperfield.cz/apps/wishlist, https://pepperfield.cz/pages/vanoce-vcas-2026, https://pepperfield.cz/pages/registrace, https://pepperfield.cz/pages/referral_doporuceni, https://pepperfield.cz/collections/vsechny-produkty and https://pepperfield.cz/collections/kampotsky-pepr and 8 others have no <title>, so Google invents the link text in results.
3 pages without a meta description
https://pepperfield.cz/apps/wishlist, https://pepperfield.cz/pages/vanoce-vcas-2026 and https://pepperfield.cz/pages/registrace have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages without an H1
https://pepperfield.cz/apps/wishlist, https://pepperfield.cz/pages/vanoce-vcas-2026, https://pepperfield.cz/pages/referral_doporuceni, https://pepperfield.cz/collections/vsechny-produkty, https://pepperfield.cz/collections/kampotsky-pepr and https://pepperfield.cz/collections/darkova-baleni and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
13 pages with very little text
https://pepperfield.cz/apps/wishlist, https://pepperfield.cz/pages/registrace, https://pepperfield.cz/pages/referral_doporuceni, https://pepperfield.cz/collections/vsechny-produkty, https://pepperfield.cz/collections/kampotsky-pepr and https://pepperfield.cz/collections/darkova-baleni and 7 others have 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 100 found) and read each the way a search engine does.
3 checks passed
Linked pages load
14 pages 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=355051351&Ver=2&mid=bcfda444-dd53-48d2-a943-0821b5aa0cb1&bo=3&sid=3bf781c0da8211f19c37b729377dab34&vid=3bf7b500da8211f1adb3a5f6a238a26f&vids=1&msclkid=N&pagetype=home&.
17 small tap targets
17 of 75 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 606 words of copy
The homepage carries about 606 words of visible text.
4 checks passed
13 short forms
13 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 18 testimonial or review blocks, 8 customer or partner logos and a star rating.
Analytics in place
Analytics detected: Microsoft Clarity and Hotjar.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads 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
22Opening the homepage sets 22 cookies, 2 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.
46 other companies contacted
Loading the homepage contacts 46 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 pepperfield.cz, 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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Wishlist Fade My Wishlist · Langshop · Judge Me Reviews · Microsoft Clarity · Trueroas · Instafeed · Gdpr Cookie Consent · Joy Loyalty Program · Stape Remix · Avada Faqs · dognet.sk
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
- jQuery
- E-commerce
- Shopify
- Analytics
- Hotjar | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on pepperfield.cz, including 19 speed issues, 2 SEO issues and 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.