Website review, no card needed
runleadgen.com website review
Visit site (opens in a new tab)Reviewed 8 November 202628 issues · 79 checks
This review found 28 issues worth fixing on runleadgen.com, 13 of them high impact, across 79 checks. The most urgent: 1 image over 500 KB. 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
79CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Improve image delivery
3.0 s · 703 KiB2 images could be 703 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.
Use efficient cache lifetimes
2.7 s · 581 KiB60 files are served with short cache lifetimes, so returning visitors download them again (581 KiB).
Render-blocking requests
2.1 s29 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Reduce unused JavaScript
1.6 s · 313 KiBAbout 313 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Main-thread work: 5.6 s
A phone's processor spends 5.6 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 56
56/100Your mobile performance score is 56. 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, Facebook and Clarity and others), adding 1.5 MB and 832 ms of main-thread time.
Google Tag Manager adds 348 ms
348 msGoogle Tag Manager costs a phone 348 ms of main-thread work and 498 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.
Cloudflare CDN adds 78 ms
78 msCloudflare CDN costs a phone 78 ms of main-thread work and 402 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
190 ms · 140 KiBAbout 140 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 190 ms faster on a phone.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 185 ms. During a long task the page ignores taps.
Legacy JavaScript
50 ms · 23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 33 ms
33 msYour server sent the HTML in 33 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 21.8 s
21.8 sYour largest element takes 21.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A Utah SEO, AEO and digital marketing agency. Get an in-hou…”.
Time to Interactive: 21.8 s
21.8 sThe page becomes fully interactive after 21.8 s. Good is under 3.8 s.
Speed Index: 6.4 s
6.4 sVisually, the page fills in at 6.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 370 ms
370 msScripts block taps and scrolling for 370 ms in total while the page loads. Good is under 200 ms.
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.005
0.005The layout barely moves while loading (CLS 0.005, good is under 0.1).
Images and page weight
1 image over 500 KB
The-last-Shanty.gif weighs 42.5 MB. On a phone connection a single image that size takes seconds.
2 images far larger than shown
12.8 MB2 images are downloaded at several times the size a phone draws them, for example The-last-Shanty.gif at 1,280 px wide, shown at 357 px. Resized copies would save about 12.8 MB.
2 images in older formats
2 images (42.7 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
2 images below the first screen load straight away
2 images further down the page (42.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
Page weight: 3.4 MB in 119 requests
3.4 MBYour homepage downloads 3.4 MB in 119 requests on a phone: scripts 1.6 MB (47), images 932 KiB (10) and fonts 432 KiB (7). Under 2 MB keeps phones on slow connections fast.
About 1.0 g of CO₂ per visit
0.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.97 g of CO₂e: 116.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
32 text elements with low contrast
32 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
All page content should be contained by landmarks (89 elements)
All page content should be contained by landmarks: 89 elements on the page fail this check, rated moderate by axe-core.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h5, h2 → h4 and h2 → 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. (2 elements).
1 checks passed
40 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: 40 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
184 internal links, 14 external
The homepage links to 184 pages on runleadgen.com and 14 external pages.
8 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “A Utah marketing agency and growth partner running SEO, AEO, paid ads, websites, CRM and AI agents as one flywheel. Eve…”.
One H1 headline
Your main headline reads: “Utah Marketing Agency & Growth Partner”.
Title: 58 characters
Your title is a healthy 58 characters: “Utah Based Marketing Agency & SEO Partner for Growth | Run”.
Canonical URL set
The canonical URL is https://rundigital.com/.
Structured data in place
Structured data found: Article, ImageObject, LocalBusiness, Organization and Person.
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://rundigital.com/sitemap_index.xml.
AI search readiness
4 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 (2,396 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://rundigital.com/llms.txt (48 KiB, 172 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
1 page without an H1
https://rundigital.com/grow-optin has no <h1> headline, so visitors and search engines get no clear main topic.
6 pages slow to respond
https://rundigital.com/grow-optin, https://rundigital.com/services/seo, https://rundigital.com/services/crm, https://rundigital.com/services/marketing-automation, https://rundigital.com/services/web-analytics and https://rundigital.com/services/search-engine-marketing took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 59 found) and read each the way a search engine does.
6 checks passed
Linked pages load
11 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 11 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 11 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
57 of 62 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 2,527 words of copy
The homepage carries about 2,527 words of visible text.
9 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book a free demo”.
10 calls to action
The homepage has 10 calls to action, for example “Contact”, “Book a free demo” and “Learn more”.
1 short form
A short form (3 fields at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 10 testimonial or review blocks, 1 customer or partner logo, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Microsoft Clarity and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 6 phone links and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.
9 cookies set on arrival
9Opening the homepage sets 9 cookies, 3 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.
31 other companies contacted
Loading the homepage contacts 31 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 runleadgen.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
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on runleadgen.com, including 14 speed issues and 1 SEO issue. 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.