Website review, no card needed
nadeensinhermitage.com website review
Visit site (opens in a new tab)Reviewed 12 November 202628 issues · 79 checks
This review found 28 issues worth fixing on nadeensinhermitage.com, 9 of them high impact, across 79 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
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.0 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 27, 2026 | 1.0 s |
| Jul 25, 2026 | 952 ms |
| Aug 1, 2026 | 965 ms |
| Aug 8, 2026 | 944 ms |
| Aug 15, 2026 | 966 ms |
| Aug 22, 2026 | 973 ms |
| Aug 29, 2026 | 979 ms |
| Sep 12, 2026 | 1.0 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.2 s |
| Nov 7, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 113 ms |
| May 30, 2026 | 111 ms |
| Jun 6, 2026 | 112 ms |
| Aug 8, 2026 | 104 ms |
| Aug 15, 2026 | 106 ms |
| Aug 22, 2026 | 110 ms |
| Oct 3, 2026 | 120 ms |
| Oct 10, 2026 | 116 ms |
| Oct 17, 2026 | 114 ms |
| Oct 24, 2026 | 112 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.2 s
2.7 s
3.3 s
3.8 s
4.4 s
Speed
Use efficient cache lifetimes
4.0 s · 1.0 MB60 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).
Improve image delivery
2.5 s · 546 KiB10 images could be 546 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.
Render-blocking requests
1.4 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, spotapps.co and Unpkg and others), adding 11.0 MB and 526 ms of main-thread time.
spotapps.co adds 245 ms
245 msspotapps.co costs a phone 245 ms of main-thread work and 10.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.
Reduce unused JavaScript
900 ms · 228 KiBAbout 228 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
300 ms · 63 KiBAbout 63 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 271 ms
271 msGoogle Tag Manager costs a phone 271 ms of main-thread work and 357 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.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 152 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
35 KiBPolyfills for old browsers add 35 KiB JavaScript that modern phones do not need.
Minify JavaScript
24 KiB24 KiB could be saved by minifying JavaScript.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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, 602 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 16.6 s
16.6 sYour largest element takes 16.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 16.6 s
16.6 sThe page becomes fully interactive after 16.6 s. Good is under 3.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.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
Total Blocking Time: 220 ms
220 msScripts block taps and scrolling for 220 ms in total while the page loads. Good is under 200 ms.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 113 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 647 ms
647 msReal visitors wait 647 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 18.1 MB in 88 requests
18.1 MBYour homepage downloads 18.1 MB in 88 requests on a phone: media 15.1 MB (1), images 2.1 MB (25) and scripts 666 KiB (29). Under 2 MB keeps phones on slow connections fast.
4 images far larger than shown
697 KiB4 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 697 KiB.
5 images in older formats
5 images (1.3 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.
2 images below the first screen load straight away
2 images further down the page (43 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 5.1 g of CO₂ per visit
5.13 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.13 g of CO₂e: 616.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 15 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
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
12 H1 headlines
There are 12 <h1> headlines (“Visit us at 3410 Lebanon Pike, Hermitage, TN 3707…”, “WELCOME TO NADEEN'S” and “*”). One clear main headline is easier for people and search engines.
14 internal links, 25 external
The homepage links to 14 pages on nadeensinhermitage.com and 25 external pages.
6 checks passed
Meta description: 129 characters
Your meta description is 129 characters: “In the heart of Hermitage, Nadeen’s brings bold, scratch-made flavors to a space built on friendship, hustle, and a sha…”.
Title: 57 characters
Your title is a healthy 57 characters: “Best Cocktail Bar in Hermitage | Nadeen's Hermitage Haven”.
Canonical URL set
The canonical URL is https://nadeensinhermitage.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://nadeensinhermitage.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://nadeensinhermitage.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 (379 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://nadeensinhermitage.com/-party and https://nadeensinhermitage.com/hermitage-nadeen-s-hermitage-haven-party all use the title “Nadeen's Hermitage Haven - Groups and Parties”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://nadeensinhermitage.com/-party, https://nadeensinhermitage.com/hermitage-nadeen-s-hermitage-haven-food-menu, https://nadeensinhermitage.com/hermitage-nadeen-s-hermitage-haven-drink-menu, https://nadeensinhermitage.com/hermitage-nadeen-s-hermitage-haven-party and https://nadeensinhermitage.com/hermitage-nadeen-s-hermitage-haven-catering have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://nadeensinhermitage.com/-party, whose canonical is https://nadeensinhermitage.com/hermitage-nadeen-s-hermitage-haven-party. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages with very little text
https://nadeensinhermitage.com/-party, https://nadeensinhermitage.com/hermitage-nadeen-s-hermitage-haven-party and https://nadeensinhermitage.com/hermitage-nadeen-s-hermitage-haven-catering 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.
7 internal pages checked
We fetched 7 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
6 pages of 7 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 6 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
33 of 41 tappable elements near the top are at least 24 px.
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.
Thin social proof
Social proof on the homepage: 25 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 543 words of copy
The homepage carries about 543 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 your party” and “ORDER”.
8 calls to action
The homepage has 8 calls to action, for example “Book your party”, “Order” and “slideshow start stop playing”.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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 nadeensinhermitage.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
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on nadeensinhermitage.com, including 15 speed issues, 2 SEO issues 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.