Website review, no card needed
potomacriverrunning.com website review
Visit site (opens in a new tab)Reviewed 10 November 202637 issues · 72 checks
This review found 37 issues worth fixing on potomacriverrunning.com, 13 of them high impact, across 72 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
75C- #72,181 of 109,350 reviewed websitesbeats 30%
- #45,865 of 61,859 online storesbeats 22%
- #43,357 of 56,401 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.0 s |
| Nov 7, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 109 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 120 ms |
| Jun 13, 2026 | 121 ms |
| Jun 20, 2026 | 122 ms |
| Jun 27, 2026 | 123 ms |
| Jul 4, 2026 | 119 ms |
| Jul 11, 2026 | 119 ms |
| Jul 18, 2026 | 117 ms |
| Jul 25, 2026 | 115 ms |
| Aug 1, 2026 | 120 ms |
| Aug 8, 2026 | 121 ms |
| Aug 15, 2026 | 124 ms |
| Aug 22, 2026 | 129 ms |
| Aug 29, 2026 | 132 ms |
| Sep 5, 2026 | 129 ms |
| Sep 12, 2026 | 130 ms |
| Sep 19, 2026 | 132 ms |
| Sep 26, 2026 | 137 ms |
| Oct 3, 2026 | 144 ms |
| Oct 10, 2026 | 147 ms |
| Oct 17, 2026 | 153 ms |
| Oct 24, 2026 | 157 ms |
| Oct 31, 2026 | 156 ms |
| Nov 7, 2026 | 158 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.9 s
1.8 s
2.7 s
3.5 s
4.4 s
5.3 s
6.2 s
7.1 s
Speed
Use efficient cache lifetimes
3.2 s · 907 KiB23 files are served with short cache lifetimes, so returning visitors download them again (907 KiB).
Reduce unused JavaScript
1.5 s · 858 KiBAbout 858 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Main-thread work: 4.4 s
A phone's processor spends 4.4 s on main-thread work while loading, 1.9 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, Facebook and Google CDN and others), adding 1.6 MB and 1.1 s of main-thread time.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Improve image delivery
450 ms · 251 KiB12 images could be 251 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 412 ms
412 msGoogle Tag Manager costs a phone 412 ms of main-thread work and 513 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.
Reduce unused CSS
350 ms · 37 KiBAbout 37 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 350 ms faster on a phone.
Google CDN adds 154 ms
154 msGoogle CDN costs a phone 154 ms of main-thread work and 539 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.
Legacy JavaScript
150 ms · 74 KiBPolyfills for old browsers add 74 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 198 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).
Duplicated JavaScript
43 KiB43 KiB JavaScript is shipped twice across bundles.
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.
1 checks passed
Server response: 30 ms
30 msYour server sent the HTML in 30 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.0 s
12.0 sYour largest element takes 12.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 23.1 s
23.1 sThe page becomes fully interactive after 23.1 s. Good is under 3.8 s.
Speed Index: 8.5 s
8.5 sVisually, the page fills in at 8.5 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 42% slower for real visitors
+42%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 109 ms to 158 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.6 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 591 ms
591 msScripts block taps and scrolling for 591 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
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: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 136 ms
136 msReal visitors wait 136 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 333 ms
333 msReal visitors wait 333 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.06
0.06The layout barely moves while loading (CLS 0.06, good is under 0.1).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 8.9 MB in 298 requests
8.9 MBYour homepage downloads 8.9 MB in 298 requests on a phone: fonts 4.9 MB (5), scripts 2.1 MB (68) and other files 1.0 MB (178). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
17 KiB1 image is downloaded at several times the size a phone draws it, for example pr_run_and_walk.webp at 1,376 px wide, shown at 390 px. Resized copies would save about 17 KiB.
1 image below the first screen load straight away
1 image further down the page (35 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.5 g of CO₂ per visit
2.52 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.52 g of CO₂e: 302.0 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
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 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
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (15 characters)
Your title is only 15 characters: “=PR= Run & Walk”. 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.
Meta description is long (224 characters)
Your meta description is 224 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
4 checks passed
Canonical URL set
The canonical URL is https://prrunandwalk.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://prrunandwalk.com/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 229 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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.
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.
llms.txt published
The site publishes https://prrunandwalk.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Best practices
1 broken image
1 image failed to load on a phone, for example https://pixel.sitescout.com/iap/238ec01516dd23b8.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
28 of 30 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 229 words
The homepage has only about 229 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 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
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SCHEDULE A SHOE FITTING” and “SHOP IT”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 3 mores (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.
27 cookies set on arrival
27Opening the homepage sets 27 cookies, 2 of them by other companies (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.
52 other companies contacted
Loading the homepage contacts 52 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 potomacriverrunning.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 4 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
afterpay.com · rise-ai.com · cloudfront.net · hextom.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Reston
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 potomacriverrunning.com, including 17 speed issues, 5 SEO issues and 4 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.