Website review, no card needed
mrporkamo.it website review
Visit site (opens in a new tab)Reviewed 9 November 202635 issues · 78 checks
This review found 35 issues worth fixing on mrporkamo.it, 18 of them high impact, across 78 checks. The most urgent: use efficient cache lifetimes. 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
65D- #116,715 of 125,987 reviewed websitesbeats 6%
- #67,809 of 70,324 online storesbeats 3%
- #61,993 of 63,870 Shopify storesbeats 2%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
5.3 s · 542 KiB16 files are served with short cache lifetimes, so returning visitors download them again (542 KiB).
Reduce unused JavaScript
2.4 s · 526 KiBAbout 526 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Improve image delivery
1.6 s · 268 KiB3 images could be 268 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.
Mobile performance score: 27
27/100Your mobile performance score is 27. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6,509 HTML elements
The page has 6,509 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 6.3 s
A phone's processor spends 6.3 s on main-thread work while loading, 1.6 s 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 (mrpianik.it, Klaviyo and Shopify and others), adding 1.6 MB and 740 ms of main-thread time.
Render-blocking requests
600 ms10 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
mrpianik.it adds 497 ms
497 msmrpianik.it costs a phone 497 ms of main-thread work and 511 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.
Legacy JavaScript
350 ms · 19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
Klaviyo adds 133 ms
133 msKlaviyo costs a phone 133 ms of main-thread work and 308 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.
Shopify adds 60 ms
60 msShopify costs a phone 60 ms of main-thread work and 702 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.
Minify JavaScript
150 ms · 20 KiB20 KiB could be saved by minifying JavaScript.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 161 ms. During a long task the page ignores taps.
Reduce unused CSS
50 ms · 12 KiBAbout 12 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 50 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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: 41 ms
41 msYour server sent the HTML in 41 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 21.6 s
21.6 sYour largest element takes 21.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 21.7 s
21.7 sThe page becomes fully interactive after 21.7 s. Good is under 3.8 s.
First Contentful Paint: 5.0 s
5.0 sThe first text or image appears after 5.0 s on a phone. Good is under 1.8 s.
Speed Index: 8.7 s
8.7 sVisually, the page fills in at 8.7 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.392
0.392The layout shifts by 0.392 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 473 ms
473 msScripts block taps and scrolling for 473 ms in total while the page loads. Good is under 200 ms.
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.
Images and page weight
Page weight: 8.9 MB in 386 requests
8.9 MBYour homepage downloads 8.9 MB in 386 requests on a phone: other files 6.4 MB (222), scripts 1.4 MB (92) and images 792 KiB (29). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
259586_1.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).
2 images far larger than shown
187 KiB2 images are downloaded at several times the size a phone draws them, for example mrpianik_ita.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 187 KiB.
1 image below the first screen load straight away
1 image further down the page (145 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.5 g of CO₂ per visit
2.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.51 g of CO₂e: 301.3 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
Certain ARIA roles must contain particular children (3 elements)
Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
ARIA role should be appropriate for the element (3 elements)
ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.
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
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
185 internal links, 14 external
The homepage links to 185 pages on mrporkamo.it and 14 external pages.
7 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Buy authentic Kiton at Mr.PianiK, authorized Kiton retailer: suits, shirts, shoes and accessories handmade in Naples. F…”.
Title: 45 characters
Your title is a healthy 45 characters: “Kiton Italy | Authorized Retailer – Mr.PianiK”.
Canonical URL set
The canonical URL is https://mrporkamo.it/.
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://mrporkamo.it/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 (2,569 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://mrporkamo.it/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
12 pages without an H1
https://mrporkamo.it/collections/suits, https://mrporkamo.it/collections/blazers, https://mrporkamo.it/collections/coats-1, https://mrporkamo.it/collections/overcoats, https://mrporkamo.it/collections/sweaters and https://mrporkamo.it/collections/polos and 6 others 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 86 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 14 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 14 pages that loaded have a <title>.
Best practices
51 small tap targets
51 of 61 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 673 words of copy
The homepage carries about 673 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop with your AI personal shopper”.
3 calls to action
The homepage has 3 calls to action, for example “Shop the latest” and “Contact Us”.
8 short forms
8 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 3 phone links and 1 email link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, 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.
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.
22 other companies contacted
Loading the homepage contacts 22 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 mrporkamo.it, 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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Tabnav Web Accessibility · Simprosys Google Shopping Feed · Klaviyo Email Marketing Sms · Neurocart Recc Ai Mrpianik It · Forms · trustpilot.com · Selleasy
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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on mrporkamo.it, including 18 speed issues, 1 SEO issue 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.