Website review, no card needed
honorstore.pl website review
Visit site (opens in a new tab)Reviewed 6 November 202632 issues · 86 checks
This review found 32 issues worth fixing on honorstore.pl, 10 of them high impact, across 86 checks. The most urgent: page weight: 10.1 MB in 288 requests. 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
86B- #11,830 of 121,527 reviewed websitesbeats 87%
- #7,221 of 68,759 online storesbeats 85%
- #6,996 of 62,655 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 130 ms |
| May 23, 2026 | 134 ms |
| May 30, 2026 | 137 ms |
| Jun 6, 2026 | 138 ms |
| Jun 13, 2026 | 138 ms |
| Jun 20, 2026 | 139 ms |
| Jun 27, 2026 | 145 ms |
| Jul 4, 2026 | 143 ms |
| Jul 11, 2026 | 143 ms |
| Jul 18, 2026 | 138 ms |
| Jul 25, 2026 | 138 ms |
| Aug 1, 2026 | 141 ms |
| Aug 8, 2026 | 143 ms |
| Aug 15, 2026 | 158 ms |
| Aug 22, 2026 | 166 ms |
| Aug 29, 2026 | 171 ms |
| Sep 5, 2026 | 180 ms |
| Sep 12, 2026 | 178 ms |
| Sep 19, 2026 | 173 ms |
| Sep 26, 2026 | 168 ms |
| Oct 3, 2026 | 161 ms |
| Oct 10, 2026 | 168 ms |
| Oct 17, 2026 | 167 ms |
| Oct 24, 2026 | 173 ms |
| Oct 31, 2026 | 176 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
5,019 HTML elements
The page has 5,019 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 79
79/100Your mobile performance score is 79. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms14 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 801 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 62 ms
62 msShopify costs a phone 62 ms of main-thread work and 320 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
150 ms · 11 KiBAbout 11 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, trustmate.io and trustmate.pro and others), adding 468 KiB and 111 ms of main-thread time.
Improve image delivery
135 KiB4 images could be 135 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 59 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
54 KiB6 files are served with short cache lifetimes, so returning visitors download them again (54 KiB).
Reduce unused JavaScript
53 KiBAbout 53 KiB of JavaScript is downloaded but never used on this page.
Duplicated JavaScript
19 KiB19 KiB JavaScript is shipped twice across bundles.
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.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 5.1 s
5.1 sYour largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 7.9 s
7.9 sThe page becomes fully interactive after 7.9 s. Good is under 3.8 s.
Tap response (INP) got 32% slower for real visitors
+32%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 130 ms to 176 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 3.8 s
3.8 sVisually, the page fills in at 3.8 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 128 ms
128 msReal visitors wait 128 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.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 673 ms
673 msReal visitors wait 673 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.021
0.021The layout barely moves while loading (CLS 0.021, good is under 0.1).
Total Blocking Time: 5 ms
5 msScripts block the page for only 5 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 10.1 MB in 288 requests
10.1 MBYour homepage downloads 10.1 MB in 288 requests on a phone: media 7.2 MB (1), images 938 KiB (41) and other files 853 KiB (124). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Slider-m_39c7eccf-8277-4f17-a50f-86c66e78a8ae.jpg 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).
About 2.9 g of CO₂ per visit
2.85 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.85 g of CO₂e: 342.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 use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Summary elements must have discernible text (1 element)
Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
15 images without alt text
15 images have no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
15 links without text
15 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (4 elements)
ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (3 elements)
Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3 and h1 → h3), 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
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 8 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
5 H1 headlines
There are 5 <h1> headlines (“”, “HONOR Weeks” and “”). One clear main headline is easier for people and search engines.
Meta description is long (189 characters)
Your meta description is 189 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:files/HonorStore-Logo-500px_b003fb58-6338-4fd9-89…”.
400 internal links, 38 external
The homepage links to 400 pages on honorstore.pl and 38 external pages.
5 checks passed
Title: 44 characters
Your title is a healthy 44 characters: “Oficjalny Polski Sklep HONOR | HONORSTORE.PL”.
Canonical URL set
The canonical URL is https://honorstore.pl/.
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://honorstore.pl/sitemap.xml.
AI search readiness
No llms.txt
There is no https://honorstore.pl/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 (2,962 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages without an H1
https://honorstore.pl/collections/smartfony, https://honorstore.pl/products/smartfon-honor-magic-v6, https://honorstore.pl/products/honor-600-pro, https://honorstore.pl/products/honor-600 and https://honorstore.pl/products/honor-600-lite have 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 74 found) and read each the way a search engine does.
6 checks passed
Linked pages load
5 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.
Every page has a meta description
All 5 pages 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 5 pages that loaded have a <title>.
Best practices
10 small tap targets
10 of 39 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to fetch”.
Requests the notification permission on page load
Requests the notification permission on page load.
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.
Thin social proof
Social proof on the homepage: 12 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 1,082 words of copy
The homepage carries about 1,082 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
2 checks passed
8 short forms
8 short forms (2 fields at most) are right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
23 other companies contacted
Loading the homepage contacts 23 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 honorstore.pl, 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
Pushowl · Rapi · Boo Eu Withdrawal Button · Loyalty Program · trustmate.io
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
- 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 32 issues on honorstore.pl, including 10 speed issues, 3 SEO issues and 4 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.