Website review, no card needed
ashburnfirerescue.org website review
Visit site (opens in a new tab)Reviewed 23 October 202635 issues · 88 checks
This review found 35 issues worth fixing on ashburnfirerescue.org, 15 of them high impact, across 88 checks. The most urgent: render-blocking requests. 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
77C- #69,485 of 125,389 reviewed websitesbeats 39%
- #44,783 of 70,171 online storesbeats 31%
- #1,112 of 2,942 WooCommerce storesbeats 57%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.9 s |
| May 9, 2026 | 2.8 s |
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.6 s |
| Jun 13, 2026 | 2.6 s |
| Jun 27, 2026 | 2.9 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 4.0 s |
| Oct 17, 2026 | 4.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Sep 26, 2026 | 102 ms |
| Oct 3, 2026 | 111 ms |
| Oct 10, 2026 | 113 ms |
| Oct 17, 2026 | 113 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
1.4 s
2.7 s
4.1 s
5.5 s
6.8 s
8.2 s
9.6 s
10.9 s
Speed
Render-blocking requests
6.2 s101 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.2 s.
Reduce unused JavaScript
1.2 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Reduce unused CSS
1.7 s · 231 KiBAbout 231 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.7 s faster on a phone.
Use efficient cache lifetimes
900 ms · 637 KiB11 files are served with short cache lifetimes, so returning visitors download them again (637 KiB).
Mobile performance score: 52
52/100Your mobile performance score is 52 (desktop: 61). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, givecloud.co and Facebook and others), adding 1.7 MB and 601 ms of main-thread time.
Google Tag Manager adds 178 ms
178 msGoogle Tag Manager costs a phone 178 ms of main-thread work and 503 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.
givecloud.co adds 144 ms
144 msgivecloud.co costs a phone 144 ms of main-thread work and 541 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 CDN adds 63 ms
63 msGoogle CDN costs a phone 63 ms of main-thread work and 348 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 168 ms. During a long task the page ignores taps.
Improve image delivery
50 ms · 48 KiB1 image could be 48 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.
Legacy JavaScript
59 KiBPolyfills for old browsers add 59 KiB JavaScript that modern phones do not need.
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.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 783 ms of it running JavaScript. That is comfortably low.
Server response: 187 ms
187 msYour server sent the HTML in 187 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 4.8 s
4.8 sReal visitors wait 4.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.5 s
4.5 sReal visitors see the first content after 4.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.5 s
3.5 sReal visitors wait 3.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 14.6 s
14.6 sYour largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (10.4 s).
Speed Index: 21.3 s
21.3 sVisually, the page fills in at 21.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 7.1 s
7.1 sThe first text or image appears after 7.1 s on a phone. Good is under 1.8 s.
Time to Interactive: 23.5 s
23.5 sThe page becomes fully interactive after 23.5 s. Good is under 3.8 s.
Largest content (LCP) got 46% slower for real visitors
+46%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.9 s to 4.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 102 ms to 113 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 114 ms
114 msReal visitors wait 114 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.
Total Blocking Time: 178 ms
178 msScripts block the page for only 178 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.065
0.065The layout barely moves while loading (CLS 0.065, good is under 0.1).
Images and page weight
Page weight: 3.9 MB in 193 requests
3.9 MBYour homepage downloads 3.9 MB in 193 requests on a phone: scripts 2.2 MB (50), images 1,021 KiB (11) and stylesheets 371 KiB (114). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.11 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.11 g of CO₂e: 132.8 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
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h1 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (8 elements).
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
11 links with vague text
11 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
8 links crawlers can't follow
8 links have no real href, so search engines can't follow them.
148 internal links, 25 external
The homepage links to 148 pages on ashburnfirerescue.org and 25 external pages.
8 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Ashburn Volunteer Fire and Rescue Department, Ashburn VA. A member of Loudoun County Fire Rescue Department. Neighbors …”.
One H1 headline
Your main headline reads: “AVFRD NEWS”.
Title: 51 characters
Your title is a healthy 51 characters: “Home - Ashburn Volunteer Fire and Rescue Department”.
Canonical URL set
The canonical URL is https://ashburnfirerescue.org/.
Structured data in place
Structured data found: Article, Organization, Person, Place and WebPage.
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://ashburnfirerescue.org/sitemap_index.xml.
AI search readiness
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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,352 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://ashburnfirerescue.org/community-services/chaplain-services, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page without a meta description
https://ashburnfirerescue.org/blog has no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://ashburnfirerescue.org/about/meet-the-team/officers, https://ashburnfirerescue.org/about/meet-the-team/life-members, https://ashburnfirerescue.org/student-event-volunteer and https://ashburnfirerescue.org/about/founders-hall-rental have no <h1> headline, so visitors and search engines get no clear main topic.
9 pages slow to respond
https://ashburnfirerescue.org/blog, https://ashburnfirerescue.org/about/meet-the-team/board-of-directors, https://ashburnfirerescue.org/about/meet-the-team/officers, https://ashburnfirerescue.org/about/meet-the-team/life-members, https://ashburnfirerescue.org/about/history and https://ashburnfirerescue.org/about/coverage-areas and 3 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 48 found) and read each the way a search engine does.
4 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 9 pages that loaded have a <title>.
Best practices
18 small tap targets
18 of 26 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
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
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: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
A 11-field form
Your longest form asks for 11 fields (0 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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.
About 988 words of copy
The homepage carries about 988 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact” and “Subscribe to Newsletter”.
14 calls to action
The homepage has 14 calls to action, for example “Contact”, “Subscribe to Newsletter” and “Shop”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and LinkedIn Insight.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight 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.
17 cookies set on arrival
17Opening the homepage sets 17 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.
19 other companies contacted
Loading the homepage contacts 19 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 ashburnfirerescue.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on ashburnfirerescue.org, including 19 speed issues, 2 SEO issues and 3 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.