Website review, no card needed

genevarock.com logo

genevarock.com website review

Visit site (opens in a new tab)Reviewed 1 November 202639 issues · 79 checks

This review found 39 issues worth fixing on genevarock.com, 18 of them high impact, across 79 checks. The most urgent: reduce unused JavaScript. 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.0 s971 msMay 9Oct 243.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.8 s
May 16, 20261.6 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.6 s
Jun 13, 20262.0 s
Jun 20, 20262.3 s
Jun 27, 20262.7 s
Jul 4, 20262.9 s
Jul 11, 20263.0 s
Jul 18, 20263.2 s
Jul 25, 20263.1 s
Aug 1, 20263.2 s
Aug 8, 20263.4 s
Aug 15, 20263.5 s
Aug 22, 20263.6 s
Aug 29, 20263.6 s
Sep 5, 20263.7 s
Sep 12, 20263.6 s
Sep 19, 20263.5 s
Sep 26, 20263.5 s
Oct 3, 20263.5 s
Oct 10, 20263.5 s
Oct 17, 20263.5 s
Oct 24, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
89 ms69 msMay 9Oct 2486 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202680 ms
May 16, 202679 ms
May 23, 202671 ms
May 30, 202675 ms
Jun 6, 202678 ms
Jun 13, 202679 ms
Jun 20, 202680 ms
Jun 27, 202681 ms
Jul 4, 202683 ms
Jul 11, 202682 ms
Jul 18, 202682 ms
Jul 25, 202683 ms
Aug 1, 202686 ms
Aug 8, 202685 ms
Aug 15, 202685 ms
Aug 22, 202684 ms
Aug 29, 202685 ms
Sep 5, 202687 ms
Sep 12, 202687 ms
Sep 19, 202686 ms
Sep 26, 202686 ms
Oct 3, 202687 ms
Oct 10, 202687 ms
Oct 17, 202687 ms
Oct 24, 202686 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 genevarock.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. genevarock.com at 0.4 s0.4 s
  2. genevarock.com at 0.9 s0.9 s
  3. genevarock.com at 1.3 s1.3 s
  4. genevarock.com at 1.7 s1.7 s
  5. genevarock.com at 2.2 s2.2 s
  6. genevarock.com at 2.6 s2.6 s
  7. genevarock.com at 3.0 s3.0 s
  8. genevarock.com at 3.5 s3.5 s

Speed

11 to fix45
  • Reduce unused JavaScript

    18.2 s · 2.3 MB

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

  • YouTube adds 1.4 s

    1.4 s

    YouTube costs a phone 1.4 s of main-thread work and 3.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Improve image delivery

    1.4 s · 431 KiB

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

  • Reduce unused CSS

    1.5 s · 214 KiB

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

  • Render-blocking requests

    1.2 s

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

  • Mobile performance score: 45

    45/100

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

  • Main-thread work: 4.4 s

    A phone's processor spends 4.4 s on main-thread work while loading, 2.3 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 (YouTube, Google Tag Manager and Facebook and others), adding 4.6 MB and 1.8 s of main-thread time.

  • Use efficient cache lifetimes

    300 ms · 197 KiB

    5 files are served with short cache lifetimes, so returning visitors download them again (197 KiB).

  • Google Tag Manager adds 168 ms

    168 ms

    Google Tag Manager costs a phone 168 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.

  • 1,961 HTML elements

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

  • Minify JavaScript

    150 ms · 24 KiB

    24 KiB could be saved by minifying JavaScript.

  • 18 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    27 KiB

    Polyfills for old browsers add 27 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.

1 checks passed
  • Server response: 36 ms

    36 ms

    Your server sent the HTML in 36 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.

  • Real-user LCP: 4.7 s

    4.7 s

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

  • Real-user FCP: 4.0 s

    4.0 s

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

  • Real-user TTFB: 3.0 s

    3.0 s

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

  • First Contentful Paint: 19.1 s

    19.1 s

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

  • Largest Contentful Paint: 61.6 s

    61.6 s

    Your largest element takes 61.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “I-80 Preservation Asphalt Paving”.

  • Speed Index: 19.1 s

    19.1 s

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

  • Time to Interactive: 64.6 s

    64.6 s

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

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

    +105%

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

  • Total Blocking Time: 407 ms

    407 ms

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

  • Tap response (INP) held steady for real visitors

    +9%

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

3 checks passed
  • Real-user INP: 88 ms

    88 ms

    Real visitors wait 88 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.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix33
  • Page weight: 22.5 MB in 206 requests

    22.5 MB

    Your homepage downloads 22.5 MB in 206 requests on a phone: images 11.5 MB (87), media 5.8 MB (1) and scripts 4.2 MB (60). Under 2 MB keeps phones on slow connections fast.

  • About 6.4 g of CO₂ per visit

    6.39 g

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

Accessibility

5 to fixGoogle 9180
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 10 tap targets too small

    10 tap targets are too small or too close together to hit reliably with a finger.

  • Frames without titles

    4 frames have no title, so screen-reader users cannot tell what they contain.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 82 images in the HTML carry an alt attribute.

  • 9 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • No XML sitemap

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 173 internal links, 7 external

    The homepage links to 173 pages on genevarock.com and 7 external pages.

7 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Geneva Rock is Utah's #1 company for concrete construction and asphalt paving. Since 1954, we have helped supply & buil…”.

  • One H1 headline

    Your main headline reads: “Utah’s Leading Supplier of Construction Products & Services”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Utah Construction Services Company | Geneva Rock Products”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, Person 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.

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

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

Other pages

3 to fix85
  • 2 pages without a meta description

    https://genevarock.com/product/product-category/aggregates and https://genevarock.com/construction-services/calculators have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://genevarock.com/construction-services/credit-application, whose canonical is https://genevarock.com/credit-application. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://genevarock.com/product/product-category/aggregates has 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 100 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

1 to fixGoogle 9292
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

  • 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

5 to fix67
  • 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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 17-field form

    Your longest form asks for 17 fields (8 required). Every extra field lowers completion.

  • Only about 33 words

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

  • No opening hours

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

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

4 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Apply for Credit”, “Contact” and “Get a Quote”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Matomo.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 genevarock.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
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager | Matomo
Hosting
WordPress.com

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on genevarock.com, including 21 speed issues, 2 SEO issues and 5 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