Website review, no card needed

rpminc.com logo

rpminc.com website review

Visit site (opens in a new tab)Reviewed 2 November 202642 issues · 85 checks

This review found 42 issues worth fixing on rpminc.com, 15 of them high impact, across 85 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

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

How it loaded on a phone

  1. rpminc.com at 0.5 s0.5 s
  2. rpminc.com at 0.9 s0.9 s
  3. rpminc.com at 1.4 s1.4 s
  4. rpminc.com at 1.9 s1.9 s
  5. rpminc.com at 2.3 s2.3 s
  6. rpminc.com at 2.8 s2.8 s
  7. rpminc.com at 3.3 s3.3 s
  8. rpminc.com at 3.7 s3.7 s

Speed

13 to fix43
  • Use efficient cache lifetimes

    28.8 s · 5.9 MB

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

  • Reduce unused JavaScript

    5.3 s · 916 KiB

    About 916 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.3 s faster on a phone.

  • Reduce unused CSS

    3.0 s · 444 KiB

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

  • Render-blocking requests

    2.8 s

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

  • Mobile performance score: 43

    43/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (q4web.com, q4cdn.com and Optanon and others), adding 1.7 MB and 1.0 s of main-thread time.

  • Minify JavaScript

    600 ms · 113 KiB

    113 KiB could be saved by minifying JavaScript.

  • q4web.com adds 495 ms

    495 ms

    q4web.com costs a phone 495 ms of main-thread work and 796 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.

  • Minify CSS

    450 ms · 84 KiB

    84 KiB could be saved by minifying CSS.

  • Improve image delivery

    418 KiB

    1 image could be 418 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Main-thread work: 3.0 s

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

  • q4cdn.com adds 179 ms

    179 ms

    q4cdn.com costs a phone 179 ms of main-thread work and 476 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.

  • 2,086 HTML elements

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

  • 9 long tasks on the main thread

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

  • Document request latency

    140 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

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

1 checks passed
  • Server response: 67 ms

    67 ms

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

Core Web Vitals

6 to fix53
  • First Contentful Paint: 12.2 s

    12.2 s

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

  • Largest Contentful Paint: 35.1 s

    35.1 s

    Your largest element takes 35.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: 35.2 s

    35.2 s

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

  • Speed Index: 14.4 s

    14.4 s

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

  • 72 images without width and height

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

  • Total Blocking Time: 500 ms

    500 ms

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

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

1 checks passed
  • Cumulative Layout Shift: 0.019

    0.019

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

Images and page weight

1 to fix70
  • Page weight: 6.6 MB in 112 requests

    6.6 MB

    Your homepage downloads 6.6 MB in 112 requests on a phone: images 4.0 MB (18), scripts 1.6 MB (45) and stylesheets 611 KiB (20). Under 2 MB keeps phones on slow connections fast.

  • About 1.9 g of CO₂ per visit

    1.87 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

6 to fixGoogle 8489
  • Invalid ARIA attributes

    4 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Images must have alternative text (3 elements)

    Images must have alternative text: 3 elements on the page fail this check, rated critical by axe-core.

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

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 17 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.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 41 automated accessibility rules passed

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

SEO

8 to fixGoogle 8273
  • No structured data

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

  • 9 H1 headlines

    There are 9 <h1> headlines (“Q1 2027 Quarterly Results”, “” and “”). One clear main headline is easier for people and search engines.

  • 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:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://rpminc.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at rpminc.com/robots.txt, the first file search crawlers ask for.

  • No favicon declared

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

  • 4 links with vague text

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

  • 408 internal links, 101 external

    The homepage links to 408 pages on rpminc.com and 101 external pages.

2 checks passed
  • Meta description: 137 characters

    Your meta description is 137 characters: “RPM International Inc. owns subsidiaries that are world leaders in specialty coatings, sealants, building materials and…”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “World Leader in Specialty Coatings | RPM International Inc.”.

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://rpminc.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

1 to fix95
  • 12 pages without an H1

    https://rpminc.com/contact-rpm, https://rpminc.com/about-rpm, https://rpminc.com/about-rpm/code-of-conduct, https://rpminc.com/about-rpm/acquisitions, https://rpminc.com/about-rpm/board-of-directors and https://rpminc.com/about-rpm/board-of-directors/julie-a-beck and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • 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

3 to fixGoogle 7385
  • 4 small tap targets

    4 of 20 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.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 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

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

  • Thin social proof

    Social proof on the homepage: 94 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

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

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

    The homepage carries about 624 words of visible text.

4 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact” and “Learn More”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 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). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies (measured from a US location before any click).

  • 14 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 rpminc.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 Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Azure

Company

Employees
9,730
Founded
1947
Headquarters
Medina

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on rpminc.com, including 19 speed issues, 8 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