Website review, no card needed
gourmetcafenj.com website review
Visit site (opens in a new tab)Reviewed 22 October 202629 issues · 80 checks
This review found 29 issues worth fixing on gourmetcafenj.com, 10 of them high impact, across 80 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
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 785 ms |
| May 9, 2026 | 826 ms |
| May 16, 2026 | 822 ms |
| May 23, 2026 | 857 ms |
| May 30, 2026 | 910 ms |
| Jun 6, 2026 | 991 ms |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 930 ms |
| Jul 11, 2026 | 858 ms |
| Jul 18, 2026 | 847 ms |
| Jul 25, 2026 | 824 ms |
| Aug 1, 2026 | 847 ms |
| Aug 8, 2026 | 830 ms |
| Aug 15, 2026 | 807 ms |
| Aug 22, 2026 | 831 ms |
| Aug 29, 2026 | 900 ms |
| Sep 5, 2026 | 971 ms |
| Sep 12, 2026 | 927 ms |
| Sep 19, 2026 | 884 ms |
| Oct 10, 2026 | 830 ms |
| Oct 17, 2026 | 866 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 128 ms |
| May 9, 2026 | 129 ms |
| May 16, 2026 | 125 ms |
| May 23, 2026 | 128 ms |
| May 30, 2026 | 128 ms |
| Jun 6, 2026 | 128 ms |
| Jun 13, 2026 | 138 ms |
| Jun 20, 2026 | 122 ms |
| Jun 27, 2026 | 120 ms |
| Jul 4, 2026 | 112 ms |
| Jul 11, 2026 | 106 ms |
| Aug 22, 2026 | 112 ms |
| Aug 29, 2026 | 117 ms |
| Sep 5, 2026 | 121 ms |
| Sep 12, 2026 | 123 ms |
| Sep 19, 2026 | 121 ms |
| Oct 10, 2026 | 114 ms |
| Oct 17, 2026 | 116 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.0 s
1.5 s
2.0 s
2.5 s
3.0 s
3.5 s
4.0 s
Speed
Improve image delivery
3.4 s · 2.0 MB12 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.4 s faster on a phone.
Use efficient cache lifetimes
4.0 s · 1.0 MB61 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).
Render-blocking requests
2.6 s19 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.6 s.
Reduce unused JavaScript
1.4 s · 224 KiBAbout 224 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 40
40/100Your mobile performance score is 40 (desktop: 75). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7 third-party services on the page
7 third-party services load with your homepage (spotapps.co, Google Tag Manager and Unpkg and others), adding 19.4 MB and 1.0 s of main-thread time.
spotapps.co adds 561 ms
561 msspotapps.co costs a phone 561 ms of main-thread work and 18.7 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.
Google Tag Manager adds 447 ms
447 msGoogle Tag Manager costs a phone 447 ms of main-thread work and 356 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.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 1.1 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 272 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 66 KiBAbout 66 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.
Minify CSS
150 ms · 9 KiB9 KiB could be saved by minifying CSS.
Legacy JavaScript
35 KiBPolyfills for old browsers add 35 KiB JavaScript that modern phones do not need.
Minify JavaScript
27 KiB27 KiB could be saved by minifying JavaScript.
Phones get a much slower page than desktops
Desktop scores 75 but mobile only 40. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 31 ms
31 msYour server sent the HTML in 31 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 17.8 s
17.8 sYour largest element takes 17.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WELCOME TO GOURMET CAFE Skip Gallery Carousel Start stop ga…”.
Time to Interactive: 18.1 s
18.1 sThe page becomes fully interactive after 18.1 s. Good is under 3.8 s.
First Contentful Paint: 5.1 s
5.1 sThe first text or image appears after 5.1 s on a phone. Good is under 1.8 s.
Speed Index: 9.7 s
9.7 sVisually, the page fills in at 9.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 465 ms
465 msScripts block taps and scrolling for 465 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.141
0.141The layout shifts by 0.141 while loading, so content jumps under the reader's thumb. Good is under 0.1.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 118 ms
118 msReal visitors wait 118 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.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 311 ms
311 msReal visitors wait 311 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-17, real Chrome visitors' tap response (inp) went from 128 ms to 116 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 19.4 MB in 101 requests
19.4 MBYour homepage downloads 19.4 MB in 101 requests on a phone: media 14.1 MB (2), images 4.3 MB (36) and scripts 666 KiB (30). Under 2 MB keeps phones on slow connections fast.
10 images in older formats
10 images (1.5 MB) 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.
12 images below the first screen load straight away
12 images further down the page (1.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images far larger than shown
459 KiB2 images are downloaded at several times the size a phone draws them, for example website_casual.jpg at 1,200 px wide, shown at 298 px. Resized copies would save about 459 KiB.
About 5.5 g of CO₂ per visit
5.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.51 g of CO₂e: 661.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 checks passed
Every image has alt text
All 97 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 0 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (249 characters)
Your meta description is 249 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Restaurant) but with 1 problem, for example “Restaurant: url is not an absolute URL ("gourmetcafenj.com")”.
30 internal links, 94 external
The homepage links to 30 pages on gourmetcafenj.com and 94 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Gourmet Cafe - Parsippany, NJ”.
Title: 57 characters
Your title is a healthy 57 characters: “Authentic Italian Restaurant in Parsippany | Gourmet Cafe”.
Canonical URL set
The canonical URL is https://gourmetcafenj.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://gourmetcafenj.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://gourmetcafenj.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 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 (814 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share 2 titles
https://gourmetcafenj.com/-catering and https://gourmetcafenj.com/catering all use the title “Gourmet Cafe - Catering”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages without a meta description
https://gourmetcafenj.com/-catering, https://gourmetcafenj.com/events, https://gourmetcafenj.com/-party, https://gourmetcafenj.com/food-menu, https://gourmetcafenj.com/lunch-and-dinner-special and https://gourmetcafenj.com/catering and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://gourmetcafenj.com/-catering, whose canonical is https://gourmetcafenj.com/catering. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages with very little text
https://gourmetcafenj.com/-catering, https://gourmetcafenj.com/-party, https://gourmetcafenj.com/catering and https://gourmetcafenj.com/party have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
11 internal pages checked
We fetched 11 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
10 pages of 11 loaded without an error (the rest turned automated requests away).
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 10 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
36 of 36 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 922 words of copy
The homepage carries about 922 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book your party” and “Open contact us popup form”.
10 calls to action
The homepage has 10 calls to action, for example “Book your party”, “Start stop gallery carousel” and “slideshow start stop playing”.
Social proof on the page
Social proof on the homepage: 25 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
12 other companies contacted
Loading the homepage contacts 12 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 gourmetcafenj.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on gourmetcafenj.com, including 17 speed issues and 2 SEO issues. 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.