Website review, no card needed

onlineoutrun.com logo

onlineoutrun.com website review

Visit site (opens in a new tab)Reviewed 10 November 202624 issues · 74 checks

This review found 24 issues worth fixing on onlineoutrun.com, 3 of them high impact, across 74 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of onlineoutrun.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. onlineoutrun.com at 0.5 s0.5 s
  2. onlineoutrun.com at 1.1 s1.1 s
  3. onlineoutrun.com at 1.6 s1.6 s
  4. onlineoutrun.com at 2.1 s2.1 s
  5. onlineoutrun.com at 2.7 s2.7 s
  6. onlineoutrun.com at 3.2 s3.2 s
  7. onlineoutrun.com at 3.8 s3.8 s
  8. onlineoutrun.com at 4.3 s4.3 s

Speed

3 to fix89
  • Render-blocking requests

    1.9 s

    43 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.

  • Mobile performance score: 89

    89/100

    Your mobile performance score is 89. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    450 ms · 87 KiB

    About 87 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, ahrefs.com and Google Fonts and others), adding 226 KiB and 132 ms of main-thread time.

  • 3 long tasks on the main thread

    3 long tasks block the main thread while loading, the longest for 107 ms. During a long task the page ignores taps.

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Reduce unused JavaScript

    95 KiB

    About 95 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    67 KiB

    54 files are served with short cache lifetimes, so returning visitors download them again (67 KiB).

  • Improve image delivery

    33 KiB

    2 images could be 33 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

  • 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.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 435 ms of it running JavaScript. That is comfortably low.

  • Server response: 44 ms

    44 ms

    Your server sent the HTML in 44 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix96
  • Speed Index: 5.6 s

    5.6 s

    Visually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 2.6 s

    2.6 s

    The first text or image appears after 2.6 s on a phone. Good is under 1.8 s.

  • Time to Interactive: 4.1 s

    4.1 s

    The page becomes fully interactive after 4.1 s. Good is under 3.8 s.

  • Largest Contentful Paint: 2.6 s

    2.6 s

    Your largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We build DR 50+ backlinks from real niche websites - no PBN…”. Most of its time is element render delay (2.3 s).

  • 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.

2 checks passed
  • Total Blocking Time: 68 ms

    68 ms

    Scripts block the page for only 68 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

100
  • 1 image below the first screen load straight away

    1 image further down the page (23 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.3 g of CO₂ per visit

    0.30 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.30 g of CO₂e: 36.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • Page weight: 1.1 MB in 108 requests

    1.1 MB

    Your homepage downloads 1.1 MB in 108 requests on a phone: scripts 441 KiB (41), fonts 367 KiB (8) and stylesheets 161 KiB (42). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 9391
  • 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.

  • All page content should be contained by landmarks (19 elements)

    All page content should be contained by landmarks: 19 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • ARIA role should be appropriate for the element (3 elements)

    ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 10 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10087
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 28 internal links, 8 external

    The homepage links to 28 pages on onlineoutrun.com and 8 external pages.

6 checks passed
  • Meta description: 136 characters

    Your meta description is 136 characters: “A link building agency that specializes in generating high quality backlinks that enhance the value, traffic and author…”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “Niche Link Building Agency | Online Outrun”.

  • Canonical URL set

    The canonical URL is https://onlineoutrun.com/.

  • Structured data in place

    Structured data found: FAQPage, ImageObject, Organization, Person and WebPage.

  • 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://onlineoutrun.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (1 of 6 facts)

    Your Organization JSON-LD is missing url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://onlineoutrun.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,881 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix81
  • 2 pages share a title

    https://onlineoutrun.com/services and https://onlineoutrun.com/link-building-services all use the title “Link Building Services | Online Outrun”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://onlineoutrun.com/services and https://onlineoutrun.com/link-building-services 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://onlineoutrun.com/services, whose canonical is https://onlineoutrun.com/link-building-services. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 6 pages without an H1

    https://onlineoutrun.com/services, https://onlineoutrun.com/blog, https://onlineoutrun.com/link-building-services, https://onlineoutrun.com/referral-program, https://onlineoutrun.com/link-building-strategy and https://onlineoutrun.com/write-for-us have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://onlineoutrun.com/contact 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.

  • 10 internal pages checked

    We fetched 10 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 10 pages we checked loaded without an error.

  • Every page has a meta description

    All 10 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

Google 100100
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

1 to fix92
  • 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.

  • About 1,153 words of copy

    The homepage carries about 1,153 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book A Call” and “Book A Free Strategy Call”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Book A Call”, “Book a Free Strategy Call” and “Book Free Strategy Call”.

  • Social proof on the page

    Social proof on the homepage: 25 testimonial or review blocks, a star rating and “more than 15 businesses”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • 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

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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.

  • 6 other companies contacted

    Loading the homepage contacts 6 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 onlineoutrun.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
Hosting
Hostinger

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on onlineoutrun.com, including 7 speed issues, 2 SEO issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25