Website review, no card needed

highlinewarren.com logo

highlinewarren.com website review

Visit site (opens in a new tab)Reviewed 18 November 202641 issues · 74 checks

This review found 41 issues worth fixing on highlinewarren.com, 19 of them high impact, across 74 checks. The most urgent: improve image delivery. 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

Real-visitor load time (LCP)75th percentile, phones
6.1 s3.6 sMay 30Nov 143.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20265.7 s
Jun 6, 20265.7 s
Jun 13, 20265.6 s
Jun 20, 20265.7 s
Jun 27, 20265.8 s
Jul 4, 20265.7 s
Jul 11, 20265.7 s
Jul 18, 20265.3 s
Jul 25, 20265.3 s
Aug 1, 20265.3 s
Aug 8, 20265.2 s
Aug 15, 20265.5 s
Aug 22, 20265.5 s
Aug 29, 20265.3 s
Sep 5, 20265.2 s
Sep 12, 20265.0 s
Sep 19, 20264.9 s
Sep 26, 20264.9 s
Oct 3, 20264.8 s
Oct 10, 20264.6 s
Oct 17, 20264.4 s
Oct 24, 20264.1 s
Oct 31, 20263.9 s
Nov 7, 20263.9 s
Nov 14, 20263.9 s
Real-visitor tap response (INP)75th percentile, phones
184 ms133 msMay 30Nov 14139 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026171 ms
Jun 6, 2026175 ms
Jun 13, 2026178 ms
Jun 20, 2026173 ms
Jun 27, 2026174 ms
Jul 4, 2026176 ms
Jul 11, 2026174 ms
Jul 18, 2026175 ms
Jul 25, 2026175 ms
Aug 1, 2026172 ms
Aug 8, 2026170 ms
Aug 15, 2026171 ms
Aug 22, 2026168 ms
Aug 29, 2026167 ms
Sep 5, 2026161 ms
Sep 12, 2026161 ms
Sep 19, 2026157 ms
Sep 26, 2026157 ms
Oct 3, 2026160 ms
Oct 10, 2026150 ms
Oct 17, 2026145 ms
Oct 24, 2026144 ms
Oct 31, 2026145 ms
Nov 7, 2026144 ms
Nov 14, 2026139 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

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

How it loaded on a phone

  1. highlinewarren.com at 0.4 s0.4 s
  2. highlinewarren.com at 0.8 s0.8 s
  3. highlinewarren.com at 1.1 s1.1 s
  4. highlinewarren.com at 1.5 s1.5 s
  5. highlinewarren.com at 1.9 s1.9 s
  6. highlinewarren.com at 2.3 s2.3 s
  7. highlinewarren.com at 2.6 s2.6 s
  8. highlinewarren.com at 3.0 s3.0 s

Speed

7 to fix68
  • Improve image delivery

    2.0 s · 573 KiB

    5 images could be 573 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.

  • Reduce unused JavaScript

    1.2 s · 189 KiB

    About 189 KiB 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.

  • Render-blocking requests

    1.0 s

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

  • Reduce unused CSS

    900 ms · 150 KiB

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

  • Mobile performance score: 68

    68/100

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

  • 2,932 HTML elements

    The page has 2,932 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Vimeo adds 59 ms

    59 ms

    Vimeo costs a phone 59 ms of main-thread work and 962 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.

  • Use efficient cache lifetimes

    150 ms · 34 KiB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Vimeo and Google Fonts), adding 1,007 KiB and 59 ms of main-thread time.

  • Minify CSS

    150 ms · 4 KiB

    4 KiB could be saved by minifying CSS.

  • 3 long tasks on the main thread

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

  • 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: 0.7 s

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

  • Server response: 19 ms

    19 ms

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

Core Web Vitals

7 to fix33
  • 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 CLS: 0.79

    0.79

    For real visitors the layout shifts by 0.79 (75th percentile). Good is under 0.1.

  • Real-user FCP: 3.2 s

    3.2 s

    Real visitors see the first content after 3.2 s (75th percentile). Good is under 1.8 s.

  • Largest Contentful Paint: 26.1 s

    26.1 s

    Your largest element takes 26.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 27.6 s

    27.6 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Real-user LCP: 3.7 s

    3.7 s

    Real visitors wait 3.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

7 checks passed
  • Real-user INP: 150 ms

    150 ms

    Real visitors wait 150 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user TTFB: 759 ms

    759 ms

    Real visitors wait 759 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 18% faster for real visitors

    -18%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 171 ms to 139 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 32% faster for real visitors

    -32%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 5.7 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Speed Index: 3.2 s

    3.2 s

    Visually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 117 ms

    117 ms

    Scripts block the page for only 117 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

5 to fix18
  • Page weight: 7.8 MB in 76 requests

    7.8 MB

    Your homepage downloads 7.8 MB in 76 requests on a phone: images 6.8 MB (36), scripts 523 KiB (9) and HTML 192 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 14 images far larger than shown

    2.5 MB

    14 images are downloaded at several times the size a phone draws them, for example MC6PBP263YUREIRFKKBHUGAESCZU at 2,194 px wide, shown at 155 px. Resized copies would save about 2.5 MB.

  • 1 image over 500 KB

    MC6PBP263YUREIRFKKBHUGAESCZU weighs 773 KiB. On a phone connection a single image that size takes seconds.

  • 15 images in older formats

    15 images (2.8 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.

  • 15 images below the first screen load straight away

    15 images further down the page (2.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.2 g of CO₂ per visit

    2.22 g

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

Accessibility

4 to fixGoogle 9095
  • 7 text elements with low contrast

    7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Heading levels should only increase by one (4 elements)

    Heading levels should only increase by one: 4 elements on the page fail this check, rated moderate by axe-core.

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

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

1 checks passed
  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 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

8 to fixGoogle 9259
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • 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: “Highline Warren”. 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.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

2 checks passed
  • 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.highlinewarren.com/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 414 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.

  • No llms.txt

    There is no https://www.highlinewarren.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

Best practices

4 to fixGoogle 5083
  • 2 small tap targets

    2 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.highlinewarren.com/assets/css/theme.css?4c450c650b' because its MIME type ('te…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix30
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

  • 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 414 words of copy

    The homepage carries about 414 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, HubSpot and Cloudflare Web Analytics.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies, 8 of them by other companies (measured from a US location before any click).

  • 17 other companies contacted

    Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Osano

    A consent management tool (Osano) loads with the page.

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 highlinewarren.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2021.

Stack

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 41 issues on highlinewarren.com, including 14 speed issues, 8 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

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