Website review, no card needed
lancasterarchery.com website review
Visit site (opens in a new tab)Reviewed 4 November 202637 issues · 82 checks
This review found 37 issues worth fixing on lancasterarchery.com, 13 of them high impact, across 82 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
83B- #26,745 of 116,071 reviewed websitesbeats 72%
- #17,828 of 66,737 online storesbeats 67%
- #17,296 of 60,921 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 153 ms |
| May 23, 2026 | 154 ms |
| May 30, 2026 | 155 ms |
| Jun 6, 2026 | 158 ms |
| Jun 13, 2026 | 158 ms |
| Jun 20, 2026 | 161 ms |
| Jun 27, 2026 | 161 ms |
| Jul 4, 2026 | 158 ms |
| Jul 11, 2026 | 156 ms |
| Jul 18, 2026 | 154 ms |
| Jul 25, 2026 | 154 ms |
| Aug 1, 2026 | 154 ms |
| Aug 8, 2026 | 155 ms |
| Aug 15, 2026 | 156 ms |
| Aug 22, 2026 | 155 ms |
| Aug 29, 2026 | 157 ms |
| Sep 5, 2026 | 157 ms |
| Sep 12, 2026 | 157 ms |
| Sep 19, 2026 | 159 ms |
| Sep 26, 2026 | 156 ms |
| Oct 3, 2026 | 155 ms |
| Oct 10, 2026 | 155 ms |
| Oct 17, 2026 | 154 ms |
| Oct 24, 2026 | 154 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.7 s
3.0 s
Speed
Reduce unused JavaScript
7.3 s · 1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.3 s faster on a phone.
Use efficient cache lifetimes
4.5 s · 844 KiB35 files are served with short cache lifetimes, so returning visitors download them again (844 KiB).
Render-blocking requests
2.8 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.
Reduce unused CSS
1.6 s · 290 KiBAbout 290 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Mobile performance score: 48
48/100Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,608 HTML elements
The page has 4,608 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, ZenDesk and ContentSquare and others), adding 2.3 MB and 1.2 s of main-thread time.
Legacy JavaScript
550 ms · 54 KiBPolyfills for old browsers add 54 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 550 ms faster on a phone.
Google Tag Manager adds 292 ms
292 msGoogle Tag Manager costs a phone 292 ms of main-thread work and 532 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.
ZenDesk adds 222 ms
222 msZenDesk costs a phone 222 ms of main-thread work and 477 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.
Yotpo adds 172 ms
172 msYotpo costs a phone 172 ms of main-thread work and 394 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 79 ms
79 msKlaviyo costs a phone 79 ms of main-thread work and 320 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
240 ms · 22 KiB22 KiB could be saved by minifying JavaScript.
Improve image delivery
209 KiB8 images could be 209 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 156 ms. During a long task the page ignores taps.
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.
1 checks passed
Server response: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 27.9 s
27.9 sYour largest element takes 27.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 30.6 s
30.6 sThe page becomes fully interactive after 30.6 s. Good is under 3.8 s.
First Contentful Paint: 6.5 s
6.5 sThe first text or image appears after 6.5 s on a phone. Good is under 1.8 s.
Speed Index: 10.9 s
10.9 sVisually, the page fills in at 10.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 330 ms
330 msScripts block taps and scrolling for 330 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 153 ms to 154 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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 INP: 155 ms
155 msReal visitors wait 155 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (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: 701 ms
701 msReal visitors wait 701 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.4 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.01
0.01The layout barely moves while loading (CLS 0.01, good is under 0.1).
Images and page weight
Page weight: 6.0 MB in 351 requests
6.0 MBYour homepage downloads 6.0 MB in 351 requests on a phone: scripts 3.2 MB (131), images 1.0 MB (36) and other files 963 KiB (154). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
11-25_Monthly_Specials_-_Shrewd_Mobile_Hero.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image far larger than shown
4 KiB1 image is downloaded at several times the size a phone draws it, for example HLR69988.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 4 KiB.
About 1.7 g of CO₂ per visit
1.71 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.71 g of CO₂e: 204.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Headings skip levels
Headings skip levels (h1 → h5, h1 → h6 and h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
43 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: 43 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (24 characters)
Your title is only 24 characters: “Lancaster Archery Supply”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
3 H1 headlines
There are 3 <h1> headlines (“Lancaster Archery Supply”, “Early Savings” and “Shrewd Archery”). One clear main headline is easier for people and search engines.
Meta description is long (251 characters)
Your meta description is 251 characters; Google truncates after about 160, so the end of your pitch is cut.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
892 internal links, 16 external
The homepage links to 892 pages on lancasterarchery.com and 16 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://lancasterarchery.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://lancasterarchery.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.
3 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 (3,414 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://lancasterarchery.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a meta description
https://lancasterarchery.com/pages/pro-shop and https://lancasterarchery.com/pages/gift-cards use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://lancasterarchery.com/pages/contact-us, https://lancasterarchery.com/pages/pro-shop, https://lancasterarchery.com/pages/gift-cards, https://lancasterarchery.com/pages/las-rewards, https://lancasterarchery.com/pages/new-hot and https://lancasterarchery.com/pages/bows and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 198 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
7 small tap targets
7 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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.”).
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
About 700 words of copy
The homepage carries about 700 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop” and “SHOP NOW”.
140 calls to action
The homepage has 140 calls to action, for example “Contact Contact”, “Pro Shop & Academy Pro Shop & Academy” and “Shop”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Ads and 1 more (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.
24 cookies set on arrival
24Opening the homepage sets 24 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.
35 other companies contacted
Loading the homepage contacts 35 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 lancasterarchery.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Webflow
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Hosting
- Cloudflare
Hiring
- Hiring
- 5 open roles
- Teams
- Pro Shop (4), Warehouse (1)
- Job board
- rippling
Company
- Employees
- 128
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on lancasterarchery.com, including 18 speed issues, 5 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.