Website review, no card needed
presapan.com website review
Visit site (opens in a new tab)Reviewed 7 November 202631 issues · 83 checks
This review found 31 issues worth fixing on presapan.com, 9 of them high impact, across 83 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
88B- #5,626 of 117,615 reviewed websitesbeats 93%
- #3,103 of 66,923 online storesbeats 93%
- #3,008 of 61,018 Shopify storesbeats 92%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 118 ms |
| May 23, 2026 | 121 ms |
| May 30, 2026 | 124 ms |
| Jun 6, 2026 | 134 ms |
| Jun 13, 2026 | 122 ms |
| Jun 20, 2026 | 120 ms |
| Jun 27, 2026 | 118 ms |
| Jul 4, 2026 | 112 ms |
| Jul 11, 2026 | 122 ms |
| Jul 18, 2026 | 133 ms |
| Jul 25, 2026 | 135 ms |
| Aug 1, 2026 | 130 ms |
| Aug 8, 2026 | 128 ms |
| Aug 15, 2026 | 123 ms |
| Aug 22, 2026 | 114 ms |
| Aug 29, 2026 | 111 ms |
| Sep 5, 2026 | 109 ms |
| Sep 12, 2026 | 107 ms |
| Sep 19, 2026 | 114 ms |
| Sep 26, 2026 | 113 ms |
| Oct 3, 2026 | 112 ms |
| Oct 10, 2026 | 119 ms |
| Oct 17, 2026 | 112 ms |
| Oct 24, 2026 | 109 ms |
| Oct 31, 2026 | 104 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.8 s
2.3 s
2.9 s
3.5 s
4.1 s
4.7 s
Speed
Improve image delivery
2.7 s · 2.7 MB9 images could be 2.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.7 s faster on a phone.
Mobile performance score: 68
68/100Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.
6 third-party services on the page
6 third-party services load with your homepage (Klaviyo, loox.io and Shopify and others), adding 3.7 MB and 213 ms of main-thread time.
Reduce unused JavaScript
300 ms · 48 KiBAbout 48 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
2,162 HTML elements
The page has 2,162 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 17 ms
17 msShopify costs a phone 17 ms of main-thread work and 1.8 MB 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.
Klaviyo adds 137 ms
137 msKlaviyo costs a phone 137 ms of main-thread work and 307 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.
cloudfront.net adds 0 ms
0 mscloudfront.net costs a phone 0 ms of main-thread work and 1.4 MB 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
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.
Use efficient cache lifetimes
150 ms · 18 KiB5 files are served with short cache lifetimes, so returning visitors download them again (18 KiB).
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 77 ms. During a long task the page ignores taps.
Render-blocking requests
50 ms12 files block the first paint until they finish downloading. Deferring or inlining them could save 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.
2 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 570 ms of it running JavaScript. That is comfortably low.
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 14.5 s
14.5 sYour largest element takes 14.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Presa Pan — stovetop tortilla press”.
Time to Interactive: 14.7 s
14.7 sThe page becomes fully interactive after 14.7 s. Good is under 3.8 s.
Speed Index: 5.6 s
5.6 sVisually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 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) 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 2.1 s to 2.0 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: 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: 98 ms
98 msReal visitors wait 98 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: 566 ms
566 msReal visitors wait 566 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 118 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 30 ms
30 msScripts block the page for only 30 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.8 MB in 215 requests
4.8 MBYour homepage downloads 4.8 MB in 215 requests on a phone: images 3.2 MB (12), other files 788 KiB (102) and scripts 522 KiB (71). Under 2 MB keeps phones on slow connections fast.
6 images far larger than shown
982 KiB6 images are downloaded at several times the size a phone draws them, for example 4_1.png at 1,581 px wide, shown at 348 px. Resized copies would save about 982 KiB.
7 images below the first screen load straight away
7 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
An image on the first screen is lazy-loaded
50_OFF_SALE_678c1445-6675-443a-a24d-a02b71467f7e.png 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 1.4 g of CO₂ per visit
1.36 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.36 g of CO₂e: 163.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
31 text elements with low contrast
31 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
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.
Table header text should not be empty (1 element)
Table header text should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
<td> elements in a large <table> do not have table headers.
<td> elements in a large <table> do not have table headers. (1 element).
2 checks passed
Every image has alt text
All 12 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 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“” and “Perfect tortillas.One pan.”). One clear main headline is easier for people and search engines.
Meta description is long (216 characters)
Your meta description is 216 characters; Google truncates after about 160, so the end of your pitch is cut.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
16 internal links, 1 external
The homepage links to 16 pages on presapan.com and 1 external page.
6 checks passed
Title: 38 characters
Your title is a healthy 38 characters: “Presa Pan - 40% Off and Free Shipping!”.
Canonical URL set
The canonical URL is https://www.presapan.com/.
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://www.presapan.com/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,448 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.presapan.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.presapan.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.presapan.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
7 pages without a meta description
https://www.presapan.com/collections/all, https://www.presapan.com/customer_authentication/redirect, https://www.presapan.com/collections/presa-pan, https://www.presapan.com/policies/shipping-policy, https://www.presapan.com/policies/refund-policy and https://www.presapan.com/policies/privacy-policy and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.presapan.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.
7 internal pages checked
We fetched 7 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 7 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.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
6 of 6 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
About 980 words of copy
The homepage carries about 980 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP PRESA PAN →”.
2 calls to action
The homepage has 2 calls to action, for example “Shop Presa Pan →” and “Buy Now $229.99$109.99”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 20 testimonial or review blocks and a star rating.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, 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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
19 other companies contacted
Loading the homepage contacts 19 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 presapan.com, 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 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Aftersell · loox.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 31 issues on presapan.com, including 13 speed issues, 3 SEO issues and 1 conversion gap. 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.