Website review, no card needed
pike22.com website review
Visit site (opens in a new tab)Reviewed 19 November 202638 issues · 69 checks
This review found 38 issues worth fixing on pike22.com, 14 of them high impact, across 69 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
63DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Reduce unused JavaScript
2.7 s · 577 KiBAbout 577 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Render-blocking requests
2.4 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.
Improve image delivery
1.0 s · 335 KiB2 images could be 335 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Mobile performance score: 47
47/100Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 906 ms. During a long task the page ignores taps.
Reduce unused CSS
480 ms · 143 KiBAbout 143 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 480 ms faster on a phone.
Legacy JavaScript
350 ms · 7 KiBPolyfills for old browsers add 7 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
Minify JavaScript
310 ms · 18 KiB18 KiB could be saved by minifying JavaScript.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 794 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
simplybook.me adds 0 ms
0 mssimplybook.me costs a phone 0 ms of main-thread work and 893 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.
2 third-party services on the page
2 third-party services load with your homepage (Google CDN and simplybook.me), adding 926 KiB and 2 ms of main-thread time.
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.
Use efficient cache lifetimes
1 KiB1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).
1 checks passed
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.2 s
11.2 sYour largest element takes 11.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Show on map Book Now”. Most of its time is resource load delay (5.5 s).
Speed Index: 14.1 s
14.1 sVisually, the page fills in at 14.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 16.7 s
16.7 sThe page becomes fully interactive after 16.7 s. Good is under 3.8 s.
Total Blocking Time: 627 ms
627 msScripts block taps and scrolling for 627 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Cumulative Layout Shift: 0.023
0.023The layout barely moves while loading (CLS 0.023, good is under 0.1).
Images and page weight
Page weight: 3.4 MB in 51 requests
3.4 MBYour homepage downloads 3.4 MB in 51 requests on a phone: scripts 958 KiB (21), other files 949 KiB (17) and fonts 903 KiB (4). Under 2 MB keeps phones on slow connections fast.
About 1.0 g of CO₂ per visit
0.96 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.96 g of CO₂e: 115.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements use prohibited ARIA attributes
Elements use prohibited ARIA attributes (2 elements).
2 checks passed
Every image has alt text
All 1 image in the HTML carry an alt attribute.
11 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 13 WCAG 2.2 A/AA and best-practice rules on the phone render: 11 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (77 characters)
Your title is 77 characters, so Google will cut it off around 60: “Pike 22 Party Venue | Event Facility for parties, showers, meetings, and more”.
Meta description is long (289 characters)
Your meta description is 289 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (ItemList and LocalBusiness) but with 1 problem, for example “LocalBusiness: review is an empty list”.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
4 checks passed
Canonical URL set
The canonical URL is https://pike22.com/v2/.
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.
XML sitemap found
Your XML sitemap is reachable at https://pike22.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://pike22.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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.
Missing source maps
Large scripts ship without source maps.
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
Only about 0 words
The homepage has only about 0 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
2 checks passed
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
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.
1 other company contacted
Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 pike22.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- OVHcloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on pike22.com, including 17 speed issues, 6 SEO issues and 7 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.