Website review, no card needed
pastaevangelists.com website review
Visit site (opens in a new tab)Reviewed 5 November 202637 issues · 81 checks
This review found 37 issues worth fixing on pastaevangelists.com, 10 of them high impact, across 81 checks. The most urgent: page weight: 5.4 MB in 173 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
83B- #27,005 of 117,615 reviewed websitesbeats 72%
- #17,851 of 66,923 online storesbeats 67%
- #17,312 of 61,018 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 134 ms |
| May 23, 2026 | 134 ms |
| May 30, 2026 | 135 ms |
| Jun 6, 2026 | 136 ms |
| Jun 13, 2026 | 138 ms |
| Jun 20, 2026 | 140 ms |
| Jun 27, 2026 | 142 ms |
| Jul 4, 2026 | 143 ms |
| Jul 11, 2026 | 144 ms |
| Jul 18, 2026 | 144 ms |
| Jul 25, 2026 | 144 ms |
| Aug 1, 2026 | 145 ms |
| Aug 8, 2026 | 146 ms |
| Aug 15, 2026 | 148 ms |
| Aug 22, 2026 | 149 ms |
| Aug 29, 2026 | 150 ms |
| Sep 5, 2026 | 150 ms |
| Sep 12, 2026 | 150 ms |
| Sep 19, 2026 | 149 ms |
| Sep 26, 2026 | 150 ms |
| Oct 3, 2026 | 153 ms |
| Oct 10, 2026 | 152 ms |
| Oct 17, 2026 | 153 ms |
| Oct 24, 2026 | 153 ms |
| Oct 31, 2026 | 152 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
500 ms · 1.9 MB15 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 930 KiB17 files are served with short cache lifetimes, so returning visitors download them again (930 KiB).
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 1.0 MB and 878 ms of main-thread time.
Render-blocking requests
750 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Reduce unused CSS
450 ms · 120 KiBAbout 120 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused JavaScript
459 KiBAbout 459 KiB of JavaScript is downloaded but never used on this page.
Font display
400 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 400 ms).
Main-thread work: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 254 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 39 KiBPolyfills for old browsers add 39 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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: 38 ms
38 msYour server sent the HTML in 38 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 17.3 s
17.3 sThe page becomes fully interactive after 17.3 s. Good is under 3.8 s.
Largest Contentful Paint: 7.1 s
7.1 sYour largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Our new autumn menu is here”.
Speed Index: 7.5 s
7.5 sVisually, the page fills in at 7.5 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.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 134 ms to 152 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 147 ms
147 msReal visitors wait 147 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: 0.6 s
0.6 sReal visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 365 ms
365 msReal visitors wait 365 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 150 ms
150 msScripts block the page for only 150 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, 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: 5.4 MB in 173 requests
5.4 MBYour homepage downloads 5.4 MB in 173 requests on a phone: images 2.9 MB (36), scripts 1.2 MB (51) and other files 633 KiB (59). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
image_27.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).
6 images in older formats
6 images (898 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.
1 image below the first screen load straight away
1 image further down the page (475 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
4 images far larger than shown
81 KiB4 images are downloaded at several times the size a phone draws them, for example image_27.png at 1,180 px wide, shown at 390 px. Resized copies would save about 81 KiB.
About 1.5 g of CO₂ per visit
1.52 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.52 g of CO₂e: 182.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
Orphan list items
Some list items are not inside a list.
6 text elements with low contrast
6 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.
12 images without alt text
12 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
1 checks passed
32 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “Pasta Evangelists | Fresh Pasta Restaurants, Delivery & Experiences”.
5 H1 headlines
There are 5 <h1> headlines (“Our new autumn menu is here”, “Dine in one of our fresh pasta restaurants” and “Enjoy our fresh pasta for delivery”). One clear main headline is easier for people and search engines.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
42 internal links, 45 external
The homepage links to 42 pages on pastaevangelists.com and 45 external pages.
6 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “Get five-star pasta delivered to your door with Pasta Evangelists. Order pasta delivery online now or opt for our resta…”.
Canonical URL set
The canonical URL is https://pastaevangelists.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://pastaevangelists.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (929 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://pastaevangelists.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
2 broken images
2 images failed to load on a phone, for example https://pastaevangelists.com/.
26 small tap targets
26 of 53 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 “TypeError: Cannot read properties of null (reading 'classList')”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 799 words of copy
The homepage carries about 799 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book a table” and “Private Events - Book Your Own”.
19 calls to action
The homepage has 19 calls to action, for example “Book a table”, “Private Events - Book Your Own” and “Sign up”.
6 short forms
6 short forms (5 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 5 testimonial or review blocks, a star rating and “over 1m customers”.
Analytics in place
Analytics detected: Google Tag Manager and Hotjar.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Hotjar, Meta Pixel and Pinterest Tag and 1 more (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
14 cookies set on arrival
14Opening the homepage sets 14 cookies (measured from a US location before any click).
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.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 pastaevangelists.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
- Vue.js
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- Shopify
Company
- Employees
- 320
- Headquarters
- London
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on pastaevangelists.com, including 14 speed issues, 3 SEO issues and 3 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.