Website review, no card needed
pinkmintlove.hu website review
Visit site (opens in a new tab)Reviewed 10 November 202634 issues · 79 checks
This review found 34 issues worth fixing on pinkmintlove.hu, 13 of them high impact, across 79 checks. The most urgent: render-blocking 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
73C- #93,161 of 126,344 reviewed websitesbeats 23%
- #57,572 of 70,441 online storesbeats 15%
- #53,778 of 63,941 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.2 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.1 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.3 s |
| Oct 24, 2026 | 3.2 s |
| Oct 31, 2026 | 3.2 s |
| Nov 7, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 211 ms |
| May 30, 2026 | 228 ms |
| Jun 6, 2026 | 277 ms |
| Jun 13, 2026 | 326 ms |
| Jun 20, 2026 | 368 ms |
| Jun 27, 2026 | 381 ms |
| Jul 4, 2026 | 403 ms |
| Jul 11, 2026 | 377 ms |
| Jul 18, 2026 | 366 ms |
| Jul 25, 2026 | 347 ms |
| Aug 1, 2026 | 354 ms |
| Aug 8, 2026 | 386 ms |
| Aug 15, 2026 | 393 ms |
| Aug 22, 2026 | 429 ms |
| Aug 29, 2026 | 436 ms |
| Sep 5, 2026 | 360 ms |
| Sep 12, 2026 | 344 ms |
| Sep 19, 2026 | 369 ms |
| Sep 26, 2026 | 441 ms |
| Oct 3, 2026 | 495 ms |
| Oct 10, 2026 | 518 ms |
| Oct 17, 2026 | 531 ms |
| Oct 24, 2026 | 503 ms |
| Oct 31, 2026 | 470 ms |
| Nov 7, 2026 | 456 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
How it loaded on a phone
0.6 s
1.2 s
1.9 s
2.5 s
3.1 s
3.7 s
4.3 s
5.0 s
Speed
Render-blocking requests
1.8 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
4,046 HTML elements
The page has 4,046 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
900 ms · 248 KiBAbout 248 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: 66
66/100Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.
Main-thread work: 3.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 742 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Google Tag Manager and willdesk.com and others), adding 727 KiB and 291 ms of main-thread time.
Improve image delivery
200 ms · 79 KiB6 images could be 79 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Use efficient cache lifetimes
200 ms · 40 KiB6 files are served with short cache lifetimes, so returning visitors download them again (40 KiB).
Legacy JavaScript
150 ms · 19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 86 ms. During a long task the page ignores taps.
Reduce unused CSS
29 KiBAbout 29 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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 75 ms
75 msYour server sent the HTML in 75 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user LCP: 6.2 s
6.2 sReal visitors wait 6.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest Contentful Paint: 14.3 s
14.3 sYour largest element takes 14.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “MAX™ - UNIVERZÁLIS THERMO CIPŐ”.
Time to Interactive: 14.3 s
14.3 sThe page becomes fully interactive after 14.3 s. Good is under 3.8 s.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 111% slower for real visitors
+111%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 211 ms to 456 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 900 ms
900 msReal visitors wait 900 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 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) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.8 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.036
0.036The layout barely moves while loading (CLS 0.036, good is under 0.1).
Total Blocking Time: 63 ms
63 msScripts block the page for only 63 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.2 MB in 194 requests
2.2 MBYour homepage downloads 2.2 MB in 194 requests on a phone: scripts 905 KiB (87), other files 792 KiB (55) and images 297 KiB (14). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.63 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.63 g of CO₂e: 75.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
79 text elements with low contrast
79 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
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.
Headings skip levels
Headings skip levels (h1 → h3 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 5 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (26 characters)
Your title is only 26 characters: “Original – PinkMintLove HU”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
One H1 headline
Your <h1> is empty.
102 internal links, 3 external
The homepage links to 102 pages on pinkmintlove.hu and 3 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://pinkmintlove.hu/.
Structured data in place
Structured data found: Organization and WebSite.
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://pinkmintlove.hu/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,228 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://pinkmintlove.hu/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
11 pages without a meta description
https://pinkmintlove.hu/collections/teli-labbelik, https://pinkmintlove.hu/collections/noi-labbelik, https://pinkmintlove.hu/collections/ferfi-labbelik, https://pinkmintlove.hu/collections/nyari-labbelik, https://pinkmintlove.hu/collections/teli-ruhazat and https://pinkmintlove.hu/collections/noi-ruhazat and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://pinkmintlove.hu/collections/sale and https://pinkmintlove.hu/products/maxcomfort-teli-thermo-cipo have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages with very little text
https://pinkmintlove.hu/collections/labbelik, https://pinkmintlove.hu/collections/teli-labbelik, https://pinkmintlove.hu/collections/noi-labbelik, https://pinkmintlove.hu/collections/ferfi-labbelik, https://pinkmintlove.hu/collections/nyari-labbelik and https://pinkmintlove.hu/collections/minden-termek 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 64 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 15 pages that loaded have a <title>.
Best practices
13 small tap targets
13 of 54 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 “TypeError: Cannot read properties of undefined (reading 'querySelector')”.
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: 1 trust badge. 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 792 words of copy
The homepage carries about 792 words of visible text.
2 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo 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.
13 cookies set on arrival
13Opening the homepage sets 13 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 pinkmintlove.hu, 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 14 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Megasplet App · Shinetrust Product Badges · Pumper Bundles · Judge Me Reviews · Sami Product Labels · Tipo Related Products · Pagefly Ai Page Builder · Globo Also Bought Cross Sell · Willdesk Live Chat Helpdesk · herculesapps.com · netlify.app · pandect.es · klaviyo.com · recapture.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 34 issues on pinkmintlove.hu, including 15 speed issues, 5 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.