Website review, no card needed

adamsrefrig.com logo

adamsrefrig.com website review

Visit site (opens in a new tab)Reviewed 14 November 202617 issues · 73 checks

This review found 17 issues worth fixing on adamsrefrig.com, 8 of them high impact, across 73 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

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

How it loaded on a phone

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

Speed

3 to fix72
  • Reduce unused JavaScript

    1.1 s · 208 KiB

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

  • Mobile performance score: 72

    72/100

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

  • Google Tag Manager adds 190 ms

    190 ms

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

  • Render-blocking requests

    250 ms

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 250 ms.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and AddToAny and others), adding 391 KiB and 211 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 45 KiB

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

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 143 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).

  • Improve image delivery

    49 KiB

    3 images could be 49 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

  • Use efficient cache lifetimes

    4 KiB

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

2 checks passed
  • Main-thread work: 1.2 s

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

4 to fix67
  • Largest Contentful Paint: 7.3 s

    7.3 s

    Your largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SCHEDULE AN APPOINTMENT”.

  • Time to Interactive: 7.4 s

    7.4 s

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

  • 30 images without width and height

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

  • Speed Index: 4.3 s

    4.3 s

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

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

3 checks passed
  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 96 ms

    96 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix63
  • Page weight: 10.0 MB in 120 requests

    10.0 MB

    Your homepage downloads 10.0 MB in 120 requests on a phone: media 8.8 MB (3), scripts 485 KiB (12) and images 441 KiB (46). Under 2 MB keeps phones on slow connections fast.

  • 3 images below the first screen load straight away

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

  • 1 image in older formats

    1 image (228 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 2.8 g of CO₂ per visit

    2.83 g

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

1 checks passed
  • 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 8690
  • 56 text elements with low contrast

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

  • Links look like plain text

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 12 images without alt text

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 links without text

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

1 checks passed
  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 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

Google 100100
  • 135 internal links, 15 external

    The homepage links to 135 pages on adamsrefrig.com and 15 external pages.

8 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Adams Refrigeration is a family-run HVAC contractor in Phoenix, AZ, serving homes and businesses since 1947. Line open …”.

  • One H1 headline

    Your main headline reads: “HVAC Contractor in Phoenix, AZ”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “HVAC Contractor Phoenix, AZ | Adams Refrigeration”.

  • Canonical URL set

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

  • Structured data in place

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

  • XML sitemap found

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

AI search readiness

100
4 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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://adamsrefrig.com/llms.txt (1 KiB, 5 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

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

  • 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

1 to fixGoogle 10093
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    44 of 45 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • No form on the homepage

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

  • About 2,446 words of copy

    The homepage carries about 2,446 words of visible text.

9 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us” and “Schedule an Appointment”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Contact Us”, “Schedule an Appointment” and “Schedule an appointment”.

  • Social proof on the page

    Social proof on the homepage: 2 testimonial or review blocks, 5 customer or partner logos, a star rating and 4 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

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

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

    3

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 4 cookies set on arrival

    4

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

  • 7 other companies contacted

    Loading the homepage contacts 7 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 adamsrefrig.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 Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 17 issues on adamsrefrig.com, including 7 speed issues. 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