neirstavern.com website review

71 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).

About 632 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.1 s faster on a phone.

6 images could be 777 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

19 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

8 third-party services load with your homepage (Google CDN, Google Tag Manager and spotapps.co and others), adding 18.1 MB and 944 ms of main-thread time.

spotapps.co costs a phone 221 ms of main-thread work and 16.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.

Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.

About 94 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.

Google CDN costs a phone 301 ms of main-thread work and 736 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.

Google Tag Manager costs a phone 249 ms of main-thread work and 355 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.

A phone's processor spends 2.4 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

29 KiB could be saved by minifying JavaScript.

7 KiB could be saved by minifying CSS.

10 long tasks block the main thread while loading, the longest for 138 ms. During a long task the page ignores taps.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

Polyfills for old browsers add 22 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

The first text or image appears after 9.8 s on a phone. Good is under 1.8 s.

Your largest element takes 22.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

The page becomes fully interactive after 22.8 s. Good is under 3.8 s.

Visually, the page fills in at 10.9 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 229 ms in total while the page loads. Good is under 200 ms.

6 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 118 ms to 109 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 19.1 MB in 113 requests on a phone: media 14.2 MB (2), images 2.6 MB (34) and scripts 1.6 MB (37). Under 2 MB keeps phones on slow connections fast.

:original weighs 516 KiB. On a phone connection a single image that size takes seconds.

15 images (1.6 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.

17 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images are downloaded at several times the size a phone draws them, for example :original at 1,599 px wide, shown at 390 px. Resized copies would save about 344 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 5.41 g of CO₂e: 648.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element hidden from screen readers can still receive keyboard focus.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 15 <h1> headlines (“map marker pin87-48 78th St, Queens, NY 11421”, “The Most Famous Bar You've Never Heard Of” and “take us to go!”). One clear main headline is easier for people and search engines.

Your meta description is 932 characters; Google truncates after about 160, so the end of your pitch is cut.

3 links have no real href, so search engines can't follow them.

The homepage links to 37 pages on neirstavern.com and 57 external pages.

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.

There is no https://neirstavern.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.

https://neirstavern.com/-party and https://neirstavern.com/queens-woodhaven-neirs-tavern-party all use the title “Neir’s Tavern - Groups and Parties”. Search engines can't tell which page to show for a search, so each competes with the others.

https://neirstavern.com/-party, https://neirstavern.com/queens-woodhaven-neirs-tavern-food-menu, https://neirstavern.com/queens-woodhaven-neirs-tavern-party, https://neirstavern.com/queens-woodhaven-neirs-tavern-communityhall, https://neirstavern.com/queens-woodhaven-neirs-tavern-press and https://neirstavern.com/queens-woodhaven-neirs-tavern-privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://neirstavern.com/-party, whose canonical is https://neirstavern.com/queens-woodhaven-neirs-tavern-party. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://neirstavern.com/-party, https://neirstavern.com/queens-woodhaven-neirs-tavern-party and https://neirstavern.com/queens-woodhaven-neirs-tavern-press 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.

We fetched 10 pages linked from your homepage and read each the way a search engine does.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

Social proof on the homepage: 31 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,236 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager 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.

Opening the homepage sets 7 cookies, 2 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.