Website review, no card needed

huntercontracting.com logo

huntercontracting.com website review

Visit site (opens in a new tab)Reviewed 18 November 202636 issues · 93 checks

This review found 36 issues worth fixing on huntercontracting.com, 11 of them high impact, across 93 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.1 s1.7 sMay 30Nov 141.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.7 s
Jul 11, 20261.8 s
Jul 18, 20261.9 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.0 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20262.1 s
Oct 31, 20262.0 s
Nov 7, 20261.9 s
Nov 14, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
95 ms70 msMay 30Nov 1478 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202676 ms
Jun 6, 202680 ms
Jun 13, 202677 ms
Jun 20, 202679 ms
Jun 27, 202679 ms
Jul 4, 202675 ms
Jul 11, 202676 ms
Jul 18, 202673 ms
Jul 25, 202676 ms
Aug 1, 202678 ms
Aug 8, 202682 ms
Aug 15, 202682 ms
Aug 22, 202679 ms
Aug 29, 202679 ms
Sep 5, 202678 ms
Sep 12, 202682 ms
Sep 19, 202685 ms
Sep 26, 202686 ms
Oct 3, 202692 ms
Oct 10, 202685 ms
Oct 17, 202680 ms
Oct 24, 202679 ms
Oct 31, 202678 ms
Nov 7, 202675 ms
Nov 14, 202678 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 huntercontracting.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. huntercontracting.com at 0.9 s0.9 s
  2. huntercontracting.com at 1.9 s1.9 s
  3. huntercontracting.com at 2.8 s2.8 s
  4. huntercontracting.com at 3.8 s3.8 s
  5. huntercontracting.com at 4.7 s4.7 s
  6. huntercontracting.com at 5.7 s5.7 s
  7. huntercontracting.com at 6.6 s6.6 s
  8. huntercontracting.com at 7.5 s7.5 s

Speed

8 to fix63
  • Render-blocking requests

    1.9 s

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Vimeo, Google Tag Manager and Google Fonts and others), adding 15.7 MB and 465 ms of main-thread time.

  • Vimeo adds 330 ms

    330 ms

    Vimeo costs a phone 330 ms of main-thread work and 15.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.

  • Mobile performance score: 63

    63/100

    Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    600 ms · 126 KiB

    About 126 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Reduce unused JavaScript

    665 KiB

    About 665 KiB of JavaScript is downloaded but never used on this page.

  • Main-thread work: 3.7 s

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

  • 1,746 HTML elements

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

  • Font display

    200 ms

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

  • 11 long tasks on the main thread

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

  • Improve image delivery

    76 KiB

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

  • Use efficient cache lifetimes

    75 KiB

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

  • Legacy JavaScript

    12 KiB

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

  • Minify CSS

    11 KiB

    11 KiB could be saved by minifying CSS.

  • Minify JavaScript

    9 KiB

    9 KiB could be saved by minifying JavaScript.

  • 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: 3 ms

    3 ms

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

  • Speed Index: 13.2 s

    13.2 s

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

  • Time to Interactive: 19.4 s

    19.4 s

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

  • Largest Contentful Paint: 5.7 s

    5.7 s

    Your largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Award-Winning General Contractor”. Most of its time is element render delay (4.9 s).

  • Real-user FCP: 2.0 s

    2.0 s

    Real visitors see the first content after 2.0 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.

  • Total Blocking Time: 260 ms

    260 ms

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    0%

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

4 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 96 ms

    96 ms

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

    0.009

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

Images and page weight

1 to fix70
  • Page weight: 18.1 MB in 147 requests

    18.1 MB

    Your homepage downloads 18.1 MB in 147 requests on a phone: other files 14.6 MB (42), scripts 1.3 MB (37) and images 1.3 MB (17). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (128 KiB) is 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 5.1 g of CO₂ per visit

    5.14 g

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

2 checks passed
  • 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

9 to fixGoogle 7888
  • Links look like plain text

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

  • 2 tap targets too small

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

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Frames without titles

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

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

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

  • Zoom is disabled

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

  • 9 links without text

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

  • 3 form fields without a label

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

  • ARIA role should be appropriate for the element (6 elements)

    ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 39 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

2 to fixGoogle 10088
  • Title is short (28 characters)

    Your title is only 28 characters: “Home - Hunter Contracting Co”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (371 characters)

    Your meta description is 371 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 158 internal links, 9 external

    The homepage links to 158 pages on huntercontracting.com and 9 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “What People Say About Hunter”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Article, GeneralContractor, ImageObject, Organization and Person.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.huntercontracting.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.huntercontracting.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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

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

Other pages

2 to fix93
  • 6 pages share a meta description

    https://www.huntercontracting.com/rob-anderson, https://www.huntercontracting.com/adam-sedgeman and https://www.huntercontracting.com/ian-shantz use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://www.huntercontracting.com/about-us, https://www.huntercontracting.com/our-history, https://www.huntercontracting.com/leadership, https://www.huntercontracting.com/max-taddei, https://www.huntercontracting.com/dig-karki and https://www.huntercontracting.com/bob-carlson and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 pages slow to respond

    https://www.huntercontracting.com/bob-carlson, https://www.huntercontracting.com/rob-anderson, https://www.huntercontracting.com/adam-sedgeman, https://www.huntercontracting.com/ian-shantz, https://www.huntercontracting.com/visio-and-values and https://www.huntercontracting.com/community and 4 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 48 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 5887
  • 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.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught (in promise) Error: Setting the playback rate is not enabled for this video.”.

  • 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

2 to fix83
  • 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.

  • Thin social proof

    Social proof on the homepage: 220 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 892 words of visible text.

7 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 3 of them by other companies (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.

  • 10 other companies contacted

    Loading the homepage contacts 10 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 huntercontracting.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
Hosting
AWS

Hiring

Hiring
1 open role
Job board
careers page

Company

Employees
483

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on huntercontracting.com, including 16 speed issues, 2 SEO issues and 2 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