Website review, no card needed

rockymtn.com logo

rockymtn.com website review

Visit site (opens in a new tab)Reviewed 20 November 202641 issues · 81 checks

This review found 41 issues worth fixing on rockymtn.com, 16 of them high impact, across 81 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
3.0 s2.2 sMay 30Nov 142.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.3 s
Jun 6, 20262.4 s
Jun 13, 20262.5 s
Jun 20, 20262.6 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.5 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.7 s
Aug 8, 20262.6 s
Aug 15, 20262.6 s
Aug 22, 20262.6 s
Aug 29, 20262.7 s
Sep 5, 20262.7 s
Sep 12, 20262.8 s
Sep 19, 20262.8 s
Sep 26, 20262.8 s
Oct 3, 20262.8 s
Oct 10, 20262.8 s
Oct 17, 20262.9 s
Oct 24, 20262.9 s
Oct 31, 20262.8 s
Nov 7, 20262.7 s
Nov 14, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
112 ms78 msMay 30Nov 14103 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202683 ms
Jun 6, 202682 ms
Jun 13, 202685 ms
Jun 20, 202685 ms
Jun 27, 202684 ms
Jul 4, 202686 ms
Jul 11, 202687 ms
Jul 18, 202687 ms
Jul 25, 202688 ms
Aug 1, 202689 ms
Aug 8, 202691 ms
Aug 15, 202695 ms
Aug 22, 202695 ms
Aug 29, 202696 ms
Sep 5, 202697 ms
Sep 12, 202696 ms
Sep 19, 202697 ms
Sep 26, 202696 ms
Oct 3, 202699 ms
Oct 10, 2026104 ms
Oct 17, 2026104 ms
Oct 24, 2026108 ms
Oct 31, 2026105 ms
Nov 7, 2026104 ms
Nov 14, 2026103 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 rockymtn.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rockymtn.com at 1.3 s1.3 s
  2. rockymtn.com at 2.5 s2.5 s
  3. rockymtn.com at 3.8 s3.8 s
  4. rockymtn.com at 5.0 s5.0 s
  5. rockymtn.com at 6.3 s6.3 s
  6. rockymtn.com at 7.6 s7.6 s
  7. rockymtn.com at 8.8 s8.8 s
  8. rockymtn.com at 10.1 s10.1 s

Speed

13 to fix10
  • Use efficient cache lifetimes

    4.7 s · 4.9 MB

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

  • Improve image delivery

    3.1 s · 4.8 MB

    12 images could be 4.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.1 s faster on a phone.

  • Reduce unused JavaScript

    2.3 s · 2.4 MB

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

  • Render-blocking requests

    3.1 s

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

  • Mobile performance score: 10

    10/100

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

  • Main-thread work: 5.4 s

    A phone's processor spends 5.4 s on main-thread work while loading, 3.0 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, Google CDN and Facebook and others), adding 4.1 MB and 2.3 s of main-thread time.

  • Google Tag Manager adds 881 ms

    881 ms

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

  • Reduce unused CSS

    900 ms · 105 KiB

    About 105 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.

  • Google CDN adds 773 ms

    773 ms

    Google CDN costs a phone 773 ms of main-thread work and 1.4 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.

  • Facebook adds 302 ms

    302 ms

    Facebook costs a phone 302 ms of main-thread work and 431 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.

  • Other Google APIs/SDKs adds 209 ms

    209 ms

    Other Google APIs/SDKs costs a phone 209 ms of main-thread work and 478 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.

  • 1,648 HTML elements

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

  • Legacy JavaScript

    150 ms · 37 KiB

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

  • 20 long tasks on the main thread

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

  • Font display

    150 ms

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

  • Minify CSS

    17 KiB

    17 KiB could be saved by minifying CSS.

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

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 23 ms

    23 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 16.6 s

    16.6 s

    Your largest element takes 16.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “RIGHT BY YOU Supporting the hardworking families in Western…”.

  • Time to Interactive: 36.4 s

    36.4 s

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

  • First Contentful Paint: 5.8 s

    5.8 s

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

  • Speed Index: 12.0 s

    12.0 s

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

  • Cumulative Layout Shift: 0.74

    0.74

    The layout shifts by 0.74 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 1.0 s

    1.0 s

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

  • Real-user LCP: 3.2 s

    3.2 s

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

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

    +25%

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

  • Real-user FCP: 2.5 s

    2.5 s

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • 12 images without width and height

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

  • Largest content (LCP) got 13% slower for real visitors

    +13%

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

2 checks passed
  • Real-user INP: 110 ms

    110 ms

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

  • Real-user CLS: 0.09

    0.09

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

Images and page weight

2 to fix60
  • Page weight: 15.2 MB in 237 requests

    15.2 MB

    Your homepage downloads 15.2 MB in 237 requests on a phone: images 7.1 MB (37), scripts 4.7 MB (96) and media 1.7 MB (1). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    11 KiB

    1 image is downloaded at several times the size a phone draws it, for example laptop-mockup-2.png at 390 px wide, shown at 120 px. Resized copies would save about 11 KiB.

  • 6 images in older formats

    6 images (365 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.

  • About 4.3 g of CO₂ per visit

    4.32 g

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

1 checks passed
  • Images load when needed

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

Accessibility

6 to fixGoogle 8993
  • 6 images without alt text

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

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

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

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

  • 9 links without text

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

  • 2 form fields without a label

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

  • Headings skip levels

    Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

4 to fixGoogle 6984
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 11 links with vague text

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

  • 4 links crawlers can't follow

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

  • 159 internal links, 11 external

    The homepage links to 159 pages on rockymtn.com and 11 external pages.

6 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “With 45 branches across Western Canada, RME is the largest new and used agriculture and construction equipment dealer. …”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “We Know Agriculture and Construction | Rocky Mountain Equipment”.

  • Canonical URL set

    The canonical URL is https://rockymtn.com/.

  • Structured data in place

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

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://rockymtn.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

3 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 (1,769 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    13 pages of 15 loaded without an error (the rest turned automated requests away).

Best practices

2 to fixGoogle 9687
  • 8 small tap targets

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

  • 4 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • A 15-field form

    Your longest form asks for 15 fields (12 required). Every extra field lowers completion.

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

    The homepage carries about 455 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More”.

  • 24 calls to action

    The homepage has 24 calls to action, for example “Learn More”, “Get a Service Quote” and “Schedule a Service”.

  • Social proof on the page

    Social proof on the homepage: 18 testimonial or review blocks and 4 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 10 cookies set on arrival

    10

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

  • 30 other companies contacted

    Loading the homepage contacts 30 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 rockymtn.com, 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
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Sucuri

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 rockymtn.com, including 25 speed issues, 4 SEO issues and 1 conversion gap. 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