Website review, no card needed

royceinvest.com logo

royceinvest.com website review

Visit site (opens in a new tab)Reviewed 20 October 202643 issues · 97 checks

This review found 43 issues worth fixing on royceinvest.com, 10 of them high impact, across 97 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

Real-visitor load time (LCP)75th percentile, phones
2.7 s2.1 sMay 2Oct 172.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.5 s
May 9, 20262.4 s
May 16, 20262.4 s
May 23, 20262.6 s
May 30, 20262.6 s
Jun 6, 20262.6 s
Jun 13, 20262.6 s
Jun 20, 20262.4 s
Jun 27, 20262.4 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.3 s
Aug 22, 20262.4 s
Aug 29, 20262.5 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.3 s
Oct 17, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
134 ms66 msMay 2Oct 1795 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202677 ms
May 9, 202679 ms
May 16, 202680 ms
May 23, 202679 ms
May 30, 202679 ms
Jun 6, 202678 ms
Jun 13, 202677 ms
Jun 20, 202675 ms
Jun 27, 202685 ms
Jul 4, 202695 ms
Jul 11, 2026118 ms
Jul 18, 2026126 ms
Jul 25, 202696 ms
Aug 1, 202695 ms
Aug 8, 202687 ms
Aug 15, 202688 ms
Aug 22, 202685 ms
Aug 29, 202681 ms
Sep 5, 202685 ms
Sep 12, 202675 ms
Sep 19, 202674 ms
Oct 3, 202678 ms
Oct 10, 202689 ms
Oct 17, 202695 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 royceinvest.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix73
  • Render-blocking requests

    1.8 s

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

  • Use efficient cache lifetimes

    800 ms · 1.6 MB

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

  • Improve image delivery

    350 ms · 1.2 MB

    9 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • Mobile performance score: 73

    73/100

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

  • Reduce unused JavaScript

    300 ms · 255 KiB

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

  • Google Tag Manager adds 204 ms

    204 ms

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Google CDN and Hotjar and others), adding 571 KiB and 377 ms of main-thread time.

  • Font display

    200 ms

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

  • 3 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 11 KiB

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

  • Minify JavaScript

    22 KiB

    22 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    22 KiB

    About 22 KiB of CSS is downloaded but never applied on this page.

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

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 560 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

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

  • Largest Contentful Paint: 6.3 s

    6.3 s

    Your largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “podcast-growth-market-dynamics”.

  • Time to Interactive: 9.2 s

    9.2 s

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Speed Index: 3.5 s

    3.5 s

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

  • 12 images without width and height

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

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

    +18%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

5 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 95 ms

    95 ms

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

  • Real-user CLS: 0.06

    0.06

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

  • Total Blocking Time: 111 ms

    111 ms

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

4 to fix50
  • 1 image over 500 KB

    QMR-Cropped.png weighs 551 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 2.3 MB in 79 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 79 requests on a phone: images 1.3 MB (29), scripts 699 KiB (26) and fonts 182 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 9 images in older formats

    9 images (1.3 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.

  • 1 image far larger than shown

    336 KiB

    1 image is downloaded at several times the size a phone draws it, for example QMR-Cropped.png at 1,440 px wide, shown at 300 px. Resized copies would save about 336 KiB.

  • 2 images below the first screen load straight away

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

  • About 0.7 g of CO₂ per visit

    0.66 g

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

Accessibility

11 to fixGoogle 5982
  • 14 text elements with low contrast

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

  • Links look like plain text

    9 links inside paragraphs rely on colour alone to stand out.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 8 images without alt text

    8 images have no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 25 elements on the page fail 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 24 form fields without a label

    24 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 11 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

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

1 checks passed
  • 31 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 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 8394
  • No structured data

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

  • 12 links crawlers can't follow

    12 links have no real href, so search engines can't follow them.

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

  • 148 internal links, 38 external

    The homepage links to 148 pages on royceinvest.com and 38 external pages.

6 checks passed
  • Meta description: 143 characters

    Your meta description is 143 characters: “Small-cap specialist with unparalleled knowledge and experience, offering distinct investment approaches to meet a vari…”.

  • One H1 headline

    Your main headline reads: “Welcome to Royce Investment Partners”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “Royce Investment Partners | Small-Cap Specialists”.

  • Canonical URL set

    The canonical URL is https://www.royceinvest.com/.

  • 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.royceinvest.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.royceinvest.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 (2,550 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 3 pages share a title

    https://www.royceinvest.com/Strategies, https://www.royceinvest.com/Strategies/vehicles and https://www.royceinvest.com/strategies/engage all use the title “Strategies and Vehicles | Royce”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 links to non-canonical URLs

    Your homepage links to 15 pages by a URL that isn't their canonical one, for example https://www.royceinvest.com/Strategies, whose canonical is https://www.royceinvest.com/strategies/default. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages share a meta description

    https://www.royceinvest.com/Strategies, https://www.royceinvest.com/Strategies/vehicles and https://www.royceinvest.com/strategies/engage use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 60 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 7380
  • 19 small tap targets

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

  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • Deprecated browser APIs

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

  • No HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

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

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • A 29-field form

    Your longest form asks for 29 fields (0 required). Every extra field lowers completion.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 519 words of copy

    The homepage carries about 519 words of visible text.

5 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact Us”, “Contact us” and “Subscribe”.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 2 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and LinkedIn Insight.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • 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
  • 5 trackers load before any consent

    5

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

  • 16 cookies set on arrival

    16

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

  • 13 other companies contacted

    Loading the homepage contacts 13 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 royceinvest.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 © 2024.

Stack

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Azure

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on royceinvest.com, including 14 speed issues, 2 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