Website review, no card needed
porronet.es website review
Visit site (opens in a new tab)Reviewed 4 November 202634 issues · 82 checks
This review found 34 issues worth fixing on porronet.es, 11 of them high impact, across 82 checks. The most urgent: improve image delivery. 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
80B- #48,916 of 125,891 reviewed websitesbeats 55%
- #32,123 of 70,296 online storesbeats 48%
- #30,850 of 63,848 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 132 ms |
| May 23, 2026 | 128 ms |
| May 30, 2026 | 123 ms |
| Jun 6, 2026 | 123 ms |
| Jun 13, 2026 | 124 ms |
| Jun 20, 2026 | 125 ms |
| Jun 27, 2026 | 128 ms |
| Jul 4, 2026 | 128 ms |
| Jul 11, 2026 | 128 ms |
| Jul 18, 2026 | 128 ms |
| Jul 25, 2026 | 128 ms |
| Aug 1, 2026 | 128 ms |
| Aug 8, 2026 | 130 ms |
| Aug 15, 2026 | 131 ms |
| Aug 22, 2026 | 132 ms |
| Aug 29, 2026 | 134 ms |
| Sep 5, 2026 | 134 ms |
| Sep 12, 2026 | 135 ms |
| Sep 19, 2026 | 137 ms |
| Sep 26, 2026 | 138 ms |
| Oct 3, 2026 | 139 ms |
| Oct 10, 2026 | 137 ms |
| Oct 17, 2026 | 134 ms |
| Oct 24, 2026 | 131 ms |
| Oct 31, 2026 | 132 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
1.6 s
3.3 s
4.9 s
6.6 s
8.2 s
9.9 s
11.5 s
13.2 s
Speed
Improve image delivery
1.0 s · 1.0 MB19 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.
Render-blocking requests
1.0 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Main-thread work: 5.1 s
A phone's processor spends 5.1 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
430 ms · 248 KiBAbout 248 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 430 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, growave.io and b-cdn.net and others), adding 1.0 MB and 447 ms of main-thread time.
Klaviyo adds 217 ms
217 msKlaviyo costs a phone 217 ms of main-thread work and 352 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.
1,503 HTML elements
The page has 1,503 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
200 ms · 86 KiB20 files are served with short cache lifetimes, so returning visitors download them again (86 KiB).
Reduce unused CSS
150 ms · 48 KiBAbout 48 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 184 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
31 KiBPolyfills for old browsers add 31 KiB JavaScript that modern phones do not need.
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: 28 ms
28 msYour server sent the HTML in 28 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 10.2 s
10.2 sVisually, the page fills in at 10.2 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 6.1 s
6.1 sYour largest element takes 6.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: 12.2 s
12.2 sThe page becomes fully interactive after 12.2 s. Good is under 3.8 s.
Total Blocking Time: 214 ms
214 msScripts block taps and scrolling for 214 ms in total while the page loads. Good is under 200 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
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 132 ms to 132 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 160 ms
160 msReal visitors wait 160 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 565 ms
565 msReal visitors wait 565 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.089
0.089The layout barely moves while loading (CLS 0.089, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 8.2 MB in 356 requests
8.2 MBYour homepage downloads 8.2 MB in 356 requests on a phone: media 4.0 MB (1), images 1.6 MB (27) and other files 1.3 MB (214). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
06_BOTINES_-STAYCOMFORTABALE-01.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).
5 images in older formats
5 images (737 KiB) 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.
5 images far larger than shown
237 KiB5 images are downloaded at several times the size a phone draws them, for example VANCONDIERESIS_PORRONETMADRID_00076_WEB_dc0f6931-eab1-4532-8 at 800 px wide, shown at 193 px. Resized copies would save about 237 KiB.
About 2.3 g of CO₂ per visit
2.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.32 g of CO₂e: 278.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
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.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h4), 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. (2 elements).
1 checks passed
Every image has alt text
All 34 images in the HTML carry an alt attribute.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (27 characters)
Your title is only 27 characters: “Calzado de Mujer – PORRONET”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
206 internal links, 6 external
The homepage links to 206 pages on porronet.es and 6 external pages.
5 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “Bienvenida a Porronet: calzado de inspiración mediterránea, elaborado en España. Estilo, comodidad y artesanía en cada …”.
Canonical URL set
The canonical URL is https://www.porronet.es/.
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://www.porronet.es/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
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.
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.
llms.txt published
The site publishes https://www.porronet.es/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages share a meta description
https://www.porronet.es/collections/sneakers-fw26, https://www.porronet.es/pages/colecciones-capsula and https://www.porronet.es/collections/city-series use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://www.porronet.es/collections/sneakers-fw26, https://www.porronet.es/pages/colecciones-capsula and https://www.porronet.es/collections/city-series 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
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.
Every page has a meta description
All 15 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 15 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
25 of 25 tappable elements near the top are at least 24 px.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 329 words of copy
The homepage carries about 329 words of visible text.
2 checks passed
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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.
17 cookies set on arrival
17Opening the homepage sets 17 cookies, 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.
38 other companies contacted
Loading the homepage contacts 38 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 porronet.es, 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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Napps · Xo Insert Code · Motive Privacy Minded Search · Growave Loyalty Wishlist · trustedshops.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
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Elche
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 porronet.es, including 13 speed issues, 4 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.