Website review, no card needed

proven.us logo

proven.us website review

Visit site (opens in a new tab)Reviewed 18 October 202617 issues · 64 checks

This review found 17 issues worth fixing on proven.us, 4 of them high impact, across 64 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 proven.us (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix86
  • Render-blocking requests

    1.9 s

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

  • Use efficient cache lifetimes

    1.1 s · 189 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (189 KiB).

  • Mobile performance score: 86

    86/100

    Your mobile performance score is 86 (desktop: 99). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    420 ms · 272 KiB

    About 272 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 420 ms faster on a phone.

  • Improve image delivery

    300 ms · 72 KiB

    4 images could be 72 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Google Tag Manager adds 248 ms

    248 ms

    Google Tag Manager costs a phone 248 ms of main-thread work and 311 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.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Hubspot and Google Analytics), adding 514 KiB and 354 ms of main-thread time.

  • 3 long tasks on the main thread

    3 long tasks block the main thread while loading, the longest for 177 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.

2 checks passed
  • Main-thread work: 1.6 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

4 to fix83
  • Time to Interactive: 7.2 s

    7.2 s

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

  • Largest Contentful Paint: 3.7 s

    3.7 s

    Your largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your Mission, Our Purpose: Proven Your Mission, Our Purpose…”.

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • 10 images without width and height

    10 images have no width and height attributes, so the layout jumps as each one loads.

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

3 checks passed
  • Total Blocking Time: 128 ms

    128 ms

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

  • Cumulative Layout Shift: 0.066

    0.066

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

  • Speed Index: 2.3 s

    2.3 s

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

Images and page weight

1 to fix70
  • Page weight: 8.4 MB in 40 requests

    8.4 MB

    Your homepage downloads 8.4 MB in 40 requests on a phone: media 7.4 MB (1), scripts 642 KiB (8) and images 178 KiB (16). Under 2 MB keeps phones on slow connections fast.

  • 3 images below the first screen load straight away

    3 images further down the page (68 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.4 g of CO₂ per visit

    2.38 g

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

2 checks passed
  • 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

Google 100100
2 checks passed
  • Every image has alt text

    All 27 images in the HTML carry an alt attribute.

  • 49 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: 49 passed and 0 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100
  • 29 internal links, 8 external

    The homepage links to 29 pages on proven.us and 8 external pages.

8 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Proven is a full-service digital consultancy empowering mission-driven organizations with strategic, human-centered tec…”.

  • One H1 headline

    Your main headline reads: “Your Mission, Our Purpose: Proven”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Strategic Digital Solutions That Make An Impact | Proven”.

  • Canonical URL set

    The canonical URL is https://proven.us/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • 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://proven.us/sitemap_index.xml.

AI search readiness

100
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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes /llms.txt (2 KiB, 24 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix98
  • 2 pages share a meta description

    /privacy-policy and /accessibility use the same meta description. A description written for each page earns more clicks.

  • 2 pages with very little text

    /contact and /accessibility have 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 17 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 to fixGoogle 10093
  • 1 JavaScript error while loading

    1 error was 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

    10 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix60
  • 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.

  • Thin social proof

    Social proof on the homepage: 11 customer or partner logos. 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 514 words of copy

    The homepage carries about 514 words of visible text.

2 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact”.

  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

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.

  • 5 other companies contacted

    Loading the homepage contacts 5 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 proven.us, 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
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 17 issues on proven.us, including 10 speed issues and 3 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