Website review, no card needed

rutherfoord.com logo

rutherfoord.com website review

Visit site (opens in a new tab)Reviewed 20 October 202645 issues · 90 checks

This review found 45 issues worth fixing on rutherfoord.com, 19 of them high impact, across 90 checks. The most urgent: use efficient cache lifetimes. 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
4.2 s3.2 sMay 2Oct 173.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.8 s
May 9, 20263.8 s
May 16, 20263.8 s
May 23, 20263.8 s
May 30, 20263.8 s
Jun 6, 20263.8 s
Jun 13, 20263.8 s
Jun 20, 20263.9 s
Jun 27, 20264.0 s
Jul 4, 20264.1 s
Jul 11, 20264.1 s
Jul 18, 20264.0 s
Jul 25, 20263.9 s
Aug 1, 20263.8 s
Aug 8, 20263.8 s
Aug 15, 20263.9 s
Aug 22, 20264.0 s
Aug 29, 20264.0 s
Sep 5, 20263.8 s
Sep 12, 20263.5 s
Sep 19, 20263.4 s
Sep 26, 20263.3 s
Oct 3, 20263.3 s
Oct 10, 20263.4 s
Oct 17, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
144 ms121 msMay 2Oct 17124 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026137 ms
May 9, 2026138 ms
May 16, 2026138 ms
May 23, 2026137 ms
May 30, 2026137 ms
Jun 6, 2026136 ms
Jun 13, 2026136 ms
Jun 20, 2026137 ms
Jun 27, 2026134 ms
Jul 4, 2026138 ms
Jul 11, 2026141 ms
Jul 18, 2026140 ms
Jul 25, 2026140 ms
Aug 1, 2026137 ms
Aug 8, 2026136 ms
Aug 15, 2026136 ms
Aug 22, 2026135 ms
Aug 29, 2026136 ms
Sep 5, 2026134 ms
Sep 12, 2026135 ms
Sep 19, 2026137 ms
Sep 26, 2026137 ms
Oct 3, 2026137 ms
Oct 10, 2026129 ms
Oct 17, 2026124 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 rutherfoord.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rutherfoord.com at 0.4 s0.4 s
  2. rutherfoord.com at 0.8 s0.8 s
  3. rutherfoord.com at 1.2 s1.2 s
  4. rutherfoord.com at 1.6 s1.6 s
  5. rutherfoord.com at 2.0 s2.0 s
  6. rutherfoord.com at 2.4 s2.4 s
  7. rutherfoord.com at 2.8 s2.8 s
  8. rutherfoord.com at 3.2 s3.2 s

Speed

14 to fix26
  • Use efficient cache lifetimes

    17.7 s · 3.5 MB

    105 files are served with short cache lifetimes, so returning visitors download them again (3.5 MB).

  • Reduce unused JavaScript

    12.8 s · 2.9 MB

    About 2.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 12.8 s faster on a phone.

  • Render-blocking requests

    4.5 s

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

  • Improve image delivery

    1.9 s · 476 KiB

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

  • Minify JavaScript

    1.1 s · 219 KiB

    219 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    1.1 s · 188 KiB

    About 188 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 26

    26/100

    Your mobile performance score is 26 (desktop: 45). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 8.0 s

    A phone's processor spends 8.0 s on main-thread work while loading, 4.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Vimeo and osano.com and others), adding 4.1 MB and 1.9 s of main-thread time.

  • Google Tag Manager adds 867 ms

    867 ms

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

  • Legacy JavaScript

    600 ms · 80 KiB

    Polyfills for old browsers add 80 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 600 ms faster on a phone.

  • Vimeo adds 294 ms

    294 ms

    Vimeo costs a phone 294 ms of main-thread work and 2.8 MB 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.

  • 20 long tasks on the main thread

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

  • Google Maps adds 160 ms

    160 ms

    Google Maps costs a phone 160 ms of main-thread work and 375 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.

  • Font display

    50 ms

    Web 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

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

10 to fix67
  • 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.

  • First Contentful Paint: 20.9 s

    20.9 s

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

  • Largest Contentful Paint: 32.7 s

    32.7 s

    Your largest element takes 32.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Our specialists in insurance, employee benefits, and retire…”.

  • Speed Index: 20.9 s

    20.9 s

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

  • Time to Interactive: 44.9 s

    44.9 s

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

  • Total Blocking Time: 2.6 s

    2.6 s

    Scripts block taps and scrolling for 2.6 s in total while the page loads. Good is under 200 ms.

  • Real-user LCP: 3.5 s

    3.5 s

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 978 ms

    978 ms

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    -8%

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

4 checks passed
  • Real-user INP: 112 ms

    112 ms

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

  • Real-user CLS: 0.00

    0.00

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

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

    -12%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix53
  • Page weight: 7.5 MB in 244 requests

    7.5 MB

    Your homepage downloads 7.5 MB in 244 requests on a phone: scripts 5.2 MB (82), images 963 KiB (38) and fonts 801 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (565 KiB) 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.

  • 3 images below the first screen load straight away

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

  • About 2.1 g of CO₂ per visit

    2.13 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

4 to fixGoogle 9694
  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (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
  • 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. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 8583
  • No meta description

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

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

  • 106 internal links, 11 external

    The homepage links to 106 pages on rutherfoord.com and 11 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Your future is limitless.”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Marsh McLennan Agency | USA Insurance Leaders”.

  • Canonical URL set

    The canonical URL is https://www.marshmma.com/us/home.html.

  • 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.marshmma.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.marshmma.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 (852 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 2 pages share a title

    / and https://www.marshmma.com/us/home.html all use the title “Marsh McLennan Agency | USA Insurance Leaders”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 10 pages without a meta description

    https://www.marshmma.com/us/home.html, https://www.marshmma.com/ca/en/home.html, https://www.marshmma.com/ca/fr/home.html, https://www.marshmma.com/us/careers/life-at-mma.html, https://www.marshmma.com/us/careers/career-opportunities.html and https://www.marshmma.com/us/careers/sales-careers.html and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 80 found) and read each the way a search engine does.

5 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 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

4 to fixGoogle 5086
  • 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.”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    14 of 15 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Only about 204 words

    The homepage has only about 204 words of visible text; thin pages give Google and first-time buyers little to go on.

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us Get in touch with our team.”, “Get in Touch” and “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, LinkedIn Insight, The Trade Desk and Xandr (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.

  • 34 cookies set on arrival

    34

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

  • 40 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
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 45 issues on rutherfoord.com, including 24 speed issues, 4 SEO 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