Website review, no card needed
newtonrunning.com website review
Visit site (opens in a new tab)Reviewed 10 November 202639 issues · 81 checks
This review found 39 issues worth fixing on newtonrunning.com, 12 of them high impact, across 81 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
80B- #37,189 of 94,278 reviewed websitesbeats 55%
- #23,501 of 50,560 online storesbeats 47%
- #22,521 of 45,694 Shopify storesbeats 44%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.0 s |
| May 30, 2026 | 1.0 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.0 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.0 s |
| Jul 11, 2026 | 1.0 s |
| Jul 18, 2026 | 1.0 s |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.1 s |
| Nov 7, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 105 ms |
| May 30, 2026 | 105 ms |
| Jun 6, 2026 | 109 ms |
| Jun 13, 2026 | 112 ms |
| Jun 20, 2026 | 107 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 97 ms |
| Jul 11, 2026 | 104 ms |
| Jul 18, 2026 | 96 ms |
| Jul 25, 2026 | 102 ms |
| Aug 1, 2026 | 104 ms |
| Aug 8, 2026 | 96 ms |
| Aug 15, 2026 | 104 ms |
| Aug 22, 2026 | 103 ms |
| Aug 29, 2026 | 98 ms |
| Sep 5, 2026 | 98 ms |
| Sep 12, 2026 | 98 ms |
| Sep 19, 2026 | 98 ms |
| Sep 26, 2026 | 104 ms |
| Oct 3, 2026 | 104 ms |
| Oct 10, 2026 | 99 ms |
| Oct 17, 2026 | 100 ms |
| Oct 24, 2026 | 102 ms |
| Oct 31, 2026 | 104 ms |
| Nov 7, 2026 | 105 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.6 s
1.3 s
1.9 s
2.6 s
3.2 s
3.8 s
4.5 s
5.1 s
Speed
Reduce unused JavaScript
3.4 s · 715 KiBAbout 715 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.4 s faster on a phone.
Improve image delivery
2.7 s · 770 KiB11 images could be 770 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.7 s faster on a phone.
Render-blocking requests
1.4 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Use efficient cache lifetimes
1.1 s · 235 KiB11 files are served with short cache lifetimes, so returning visitors download them again (235 KiB).
Mobile performance score: 49
49/100Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and Klaviyo and others), adding 1.7 MB and 1.2 s of main-thread time.
Google Tag Manager adds 524 ms
524 msGoogle Tag Manager costs a phone 524 ms of main-thread work and 625 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
470 ms · 62 KiBAbout 62 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 470 ms faster on a phone.
Legacy JavaScript
300 ms · 30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 229 ms
229 msShopify costs a phone 229 ms of main-thread work and 333 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 145 ms
145 msKlaviyo costs a phone 145 ms of main-thread work and 310 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.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 243 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).
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: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 21.7 s
21.7 sYour largest element takes 21.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 21.9 s
21.9 sThe page becomes fully interactive after 21.9 s. Good is under 3.8 s.
Speed Index: 10.6 s
10.6 sVisually, the page fills in at 10.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 517 ms
517 msScripts block taps and scrolling for 517 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 105 ms to 105 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 98 ms
98 msReal visitors wait 98 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.
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: 464 ms
464 msReal visitors wait 464 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.2 MB in 238 requests
4.2 MBYour homepage downloads 4.2 MB in 238 requests on a phone: scripts 1.9 MB (89), images 1.2 MB (24) and other files 776 KiB (101). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
BiBLDR_header3_9cdefd3d-76a9-465b-b2df-966ef5fcf5c3.png weighs 494 KiB. On a phone connection a single image that size takes seconds.
2 images far larger than shown
463 KiB2 images are downloaded at several times the size a phone draws them, for example BiBLDR_header3_9cdefd3d-76a9-465b-b2df-966ef5fcf5c3.png at 2,880 px wide, shown at 390 px. Resized copies would save about 463 KiB.
4 images below the first screen load straight away
4 images further down the page (205 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.19 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.19 g of CO₂e: 143.4 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
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 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 structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“Born In Boulder” and “Striding Towards Sustainability”). One clear main headline is easier for people and search engines.
Meta description is long (237 characters)
Your meta description is 237 characters; Google truncates after about 160, so the end of your pitch is cut.
77 internal links, 5 external
The homepage links to 77 pages on newtonrunning.com and 5 external pages.
5 checks passed
Title: 39 characters
Your title is a healthy 39 characters: “Newton Running – Newton Running Company”.
Canonical URL set
The canonical URL is https://www.newtonrunning.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://www.newtonrunning.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 (265 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.newtonrunning.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://www.newtonrunning.com/collections/womens-gear and https://www.newtonrunning.com/collections/womens-gear/filter-type-bottom all use the title “Women's Gear – Newton Running Company”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.newtonrunning.com/pages/shoe-finder has no meta description, so Google writes the search snippet from whatever text it finds.
10 pages share a meta description
https://www.newtonrunning.com/collections/womens-shoes-v2, https://www.newtonrunning.com/collections/womens-shoes-v2/filter-type-training, https://www.newtonrunning.com/collections/womens-shoes-v2/filter-type-race, https://www.newtonrunning.com/collections/womens-shoes-v2/filter-type-trail, https://www.newtonrunning.com/collections/womens-shoes-v2/filter-support-neutral and https://www.newtonrunning.com/collections/womens-shoes-v2/filter-support-stability use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.newtonrunning.com/collections/womens-gear/filter-type-bottom, whose canonical is https://www.newtonrunning.com/collections/womens-gear. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
7 pages without an H1
https://www.newtonrunning.com/collections/womens-shoes-v2, https://www.newtonrunning.com/collections/womens-shoes-v2/filter-type-training, https://www.newtonrunning.com/collections/womens-shoes-v2/filter-type-race, https://www.newtonrunning.com/collections/womens-shoes-v2/filter-type-trail, https://www.newtonrunning.com/collections/womens-shoes-v2/filter-support-neutral and https://www.newtonrunning.com/collections/womens-shoes-v2/filter-support-stability and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.newtonrunning.com/pages/shoe-finder has 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 49 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17536037&Ver=2&mid=cf9f7467-945b-41b7-8020-c777361229f0&bo=1&sid=92bb8d60dcf411f18ba7d72b448985d9&vid=92bbd130dcf411f1a014031da7903b85&vids=1&msclkid=N&pi=918639831&lg.
9 small tap targets
9 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 4 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
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.
About 264 words of copy
The homepage carries about 264 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Women's” and “Shop Men's”.
5 calls to action
The homepage has 5 calls to action, for example “Shop Women's”, “Shop Men's” and “Contact Customer Service”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel 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.
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.
32 other companies contacted
Loading the homepage contacts 32 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 newtonrunning.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
Klaviyo Email Marketing Sms · Gift Card Hero All In One · Judge Me Reviews · Rez Preorder Back In Stock
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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Boulder
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on newtonrunning.com, including 18 speed issues, 3 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.