Website review, no card needed
frontporchpantry.com website review
Visit site (opens in a new tab)Reviewed 7 November 202646 issues · 94 checks
This review found 46 issues worth fixing on frontporchpantry.com, 14 of them high impact, across 94 checks. The most urgent: reduce unused JavaScript. 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
76C- #76,330 of 126,031 reviewed websitesbeats 35%
- #48,563 of 70,337 online storesbeats 26%
- #45,960 of 63,874 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 104 ms |
| May 23, 2026 | 107 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 114 ms |
| Jun 13, 2026 | 120 ms |
| Jun 20, 2026 | 122 ms |
| Jun 27, 2026 | 124 ms |
| Jul 4, 2026 | 127 ms |
| Jul 11, 2026 | 127 ms |
| Jul 18, 2026 | 126 ms |
| Jul 25, 2026 | 127 ms |
| Aug 1, 2026 | 127 ms |
| Aug 8, 2026 | 128 ms |
| Aug 15, 2026 | 129 ms |
| Aug 22, 2026 | 129 ms |
| Aug 29, 2026 | 129 ms |
| Sep 5, 2026 | 133 ms |
| Sep 12, 2026 | 136 ms |
| Sep 19, 2026 | 138 ms |
| Sep 26, 2026 | 139 ms |
| Oct 3, 2026 | 141 ms |
| Oct 10, 2026 | 145 ms |
| Oct 17, 2026 | 145 ms |
| Oct 24, 2026 | 146 ms |
| Oct 31, 2026 | 154 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.5 s
1.1 s
1.6 s
2.1 s
2.7 s
3.2 s
3.7 s
4.3 s
Speed
Reduce unused JavaScript
2.5 s · 432 KiBAbout 432 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.
Render-blocking requests
2.1 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Use efficient cache lifetimes
1.1 s · 207 KiB15 files are served with short cache lifetimes, so returning visitors download them again (207 KiB).
Mobile performance score: 56
56/100Your mobile performance score is 56. 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 (Klaviyo, Google Tag Manager and Clarity and others), adding 1.4 MB and 665 ms of main-thread time.
Improve image delivery
350 ms · 173 KiB6 images could be 173 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Reduce unused CSS
450 ms · 38 KiBAbout 38 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.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 179 ms
179 msGoogle Tag Manager costs a phone 179 ms of main-thread work and 510 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.
Klaviyo adds 182 ms
182 msKlaviyo costs a phone 182 ms of main-thread work and 342 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 78 ms
78 msShopify costs a phone 78 ms of main-thread work and 433 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 · 12 KiB12 KiB could be saved by minifying JavaScript.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 117 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
28 KiBPolyfills for old browsers add 28 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.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 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.
Largest Contentful Paint: 15.5 s
15.5 sYour largest element takes 15.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 16.2 s
16.2 sThe page becomes fully interactive after 16.2 s. Good is under 3.8 s.
Speed Index: 9.8 s
9.8 sVisually, the page fills in at 9.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Real-user CLS: 0.14
0.14For real visitors the layout shifts by 0.14 (75th percentile). Good is under 0.1.
Tap response (INP) got 42% slower for real visitors
+42%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 104 ms to 154 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
31 images without width and height
31 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 170 ms
170 msReal visitors wait 170 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 693 ms
693 msReal visitors wait 693 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 155 ms
155 msScripts block the page for only 155 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.2 MB in 322 requests
3.2 MBYour homepage downloads 3.2 MB in 322 requests on a phone: scripts 1.4 MB (97), other files 1.1 MB (170) and images 393 KiB (25). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (45 KiB) is 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 (45 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 108.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (61 elements)
All page content should be contained by landmarks: 61 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
62 form fields without a label
62 form fields have no label, so screen readers announce an empty box and autofill guesses.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 11 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (Organization, Store and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("frontporchpantry.com")”.
7 links crawlers can't follow
7 links have no real href, so search engines can't follow them.
55 internal links, 11 external
The homepage links to 55 pages on frontporchpantry.com and 11 external pages.
7 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “High quality, delicious meals delivered directly to your front porch! New deals daily and new menus weekly! No subscrip…”.
One H1 headline
Your main headline reads: “Front Porch Pantry - Fresh, Delicious Prepared Meals Delivered to Your Door”.
Title: 52 characters
Your title is a healthy 52 characters: “Front Porch Pantry | The Best Meal Delivery Service!”.
Canonical URL set
The canonical URL is https://frontporchpantry.com/.
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://frontporchpantry.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, sameAs (social profiles) and contact details; logo and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (922 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://frontporchpantry.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://frontporchpantry.com/pages/our-story and https://frontporchpantry.com/pages/press all use the title “Chef Inspired Meal Delivery Story: How We Started”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://frontporchpantry.com/blogs/news has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://frontporchpantry.com/pages/our-story and https://frontporchpantry.com/pages/press use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://frontporchpantry.com/pages/press, whose canonical is https://frontporchpantry.com/pages/our-story. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://frontporchpantry.com/pages/rewards and https://frontporchpantry.com/blogs/news have no <h1> headline, so visitors and search engines get no clear main topic.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 13 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56282108&Ver=2&mid=e45ae657-a413-4d50-b0cc-da9e68deb155&bo=1&sid=df0db120da7811f1807a03c5ac7c2003&vid=df0dd880da7811f1a44ce165a1c37ad7&vids=1&msclkid=N&pi=918639831&lg.
2 small tap targets
2 of 10 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 “Uncaught TypeError: Cannot set properties of null (setting 'innerHTML')”.
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 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.
Thin social proof
Social proof on the homepage: 128 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 644 words of copy
The homepage carries about 644 words of visible text.
5 checks passed
4 calls to action
The homepage has 4 calls to action, for example “SIGN UP”, “Try These Tasty Meals Today” and “Contact Us”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Opening hours shown
Your opening hours are on the homepage.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 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.
30 cookies set on arrival
30Opening the homepage sets 30 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.
42 other companies contacted
Loading the homepage contacts 42 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 frontporchpantry.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 14 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Judge Me Reviews · Microsoft Clarity · Mida Fraud Ip Blocker · Klaviyo Email Marketing Sms · Seo Manager Venntov · Minmaxify Order Limits · Uppromote Affiliate · Quick Announcement Bar Prod · Affliate By Secomapp · Selleasy · Easy Tabs Product Tabs · Loyalty Program · cloudfront.net · hextom.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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on frontporchpantry.com, including 19 speed issues, 2 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.