Website review, no card needed

agriframes.us logo

agriframes.us website review

Visit site (opens in a new tab)Reviewed 8 November 202635 issues · 86 checks

This review found 35 issues worth fixing on agriframes.us, 7 of them high impact, across 86 checks. The most urgent: main-thread work: 6.6 s. 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
1.9 s1.6 sMay 16Oct 311.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.8 s
Oct 24, 20261.9 s
Oct 31, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
108 ms75 msMay 16Oct 31103 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202679 ms
May 23, 202680 ms
May 30, 202681 ms
Jun 6, 202681 ms
Jun 13, 202681 ms
Jun 20, 202684 ms
Jun 27, 202687 ms
Jul 4, 202692 ms
Jul 11, 202695 ms
Jul 18, 202696 ms
Jul 25, 202696 ms
Aug 1, 202695 ms
Aug 8, 202696 ms
Aug 15, 202695 ms
Aug 22, 202696 ms
Aug 29, 202697 ms
Sep 5, 202697 ms
Sep 12, 2026104 ms
Sep 19, 2026104 ms
Sep 26, 2026103 ms
Oct 3, 2026103 ms
Oct 10, 202696 ms
Oct 17, 2026100 ms
Oct 24, 2026102 ms
Oct 31, 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 agriframes.us (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. agriframes.us at 1.3 s1.3 s
  2. agriframes.us at 2.6 s2.6 s
  3. agriframes.us at 3.8 s3.8 s
  4. agriframes.us at 5.1 s5.1 s
  5. agriframes.us at 6.4 s6.4 s
  6. agriframes.us at 7.7 s7.7 s
  7. agriframes.us at 9.0 s9.0 s
  8. agriframes.us at 10.2 s10.2 s

Speed

12 to fix77
  • Main-thread work: 6.6 s

    A phone's processor spends 6.6 s on main-thread work while loading, 3.2 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 (Shopify, Google Tag Manager and Clarity and others), adding 2.1 MB and 1.3 s of main-thread time.

  • Mobile performance score: 77

    77/100

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

  • Render-blocking requests

    950 ms

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

  • Improve image delivery

    739 KiB

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

  • Reduce unused JavaScript

    668 KiB

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

  • Shopify adds 386 ms

    386 ms

    Shopify costs a phone 386 ms of main-thread work and 622 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.

  • Use efficient cache lifetimes

    392 KiB

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

  • 14 long tasks on the main thread

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

  • 2,080 HTML elements

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

  • Stamped.io adds 110 ms

    110 ms

    Stamped.io costs a phone 110 ms of main-thread work and 623 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.

  • azurefd.net adds 81 ms

    81 ms

    azurefd.net costs a phone 81 ms of main-thread work and 321 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.

  • Reduce unused CSS

    102 KiB

    About 102 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    40 KiB

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 21 ms

    21 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 20.3 s

    20.3 s

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

  • Speed Index: 8.6 s

    8.6 s

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

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

    +29%

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

  • Total Blocking Time: 539 ms

    539 ms

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

  • 3 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user INP: 103 ms

    103 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 354 ms

    354 ms

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

  • First Contentful Paint: 1.5 s

    1.5 s

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

  • Cumulative Layout Shift: 0

    0

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

  • Largest Contentful Paint: 1.5 s

    1.5 s

    Your largest element renders in 1.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Agriframes have been leading designers of stylish, high-qua…”.

Images and page weight

4 to fix52
  • Page weight: 5.9 MB in 440 requests

    5.9 MB

    Your homepage downloads 5.9 MB in 440 requests on a phone: scripts 2.0 MB (108), images 1.8 MB (26) and other files 1.6 MB (284). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    regency-zinc-planter-wide-hero.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 2 images far larger than shown

    459 KiB

    2 images are downloaded at several times the size a phone draws them, for example 253019_7853446955216.webp at 1,000 px wide, shown at 50 px. Resized copies would save about 459 KiB.

  • 7 images below the first screen load straight away

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

  • 2 images in older formats

    2 images (146 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 1.7 g of CO₂ per visit

    1.67 g

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

Accessibility

5 to fixGoogle 8492
  • Hidden but focusable

    8 elements hidden from screen readers can still receive keyboard focus.

  • 8 text elements with low contrast

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

  • 4 images without alt text

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

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

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

  • 6 links without text

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

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

3 to fixGoogle 8589
  • No structured data

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

  • Meta description is long (255 characters)

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

  • 6 links crawlers can't follow

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

  • 136 internal links, 10 external

    The homepage links to 136 pages on agriframes.us and 10 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Agriframes USA”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Agriframes USA | 50 Years of Classic English Garden Structures”.

  • Canonical URL set

    The canonical URL is https://www.agriframes.us/.

  • 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.agriframes.us/sitemap.xml.

AI search readiness

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

  • Some text only appears after JavaScript runs

    53%

    The HTML your server sends has 816 of the 1,540 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

    There is no https://www.agriframes.us/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

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

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

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 6 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 6 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 19 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “AbortError: signal is aborted without reason”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix89
  • 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: 7 testimonial or review blocks. 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 map or directions link

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

  • About 1,540 words of copy

    The homepage carries about 1,540 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW” and “Shop now”.

  • 19 calls to action

    The homepage has 19 calls to action, for example “Contact Us”, “Shop Now” and “Shop now”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics, Meta Pixel and Microsoft Clarity.

  • Direct contact links

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

  • Phone number on the homepage

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

  • 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

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies, 1 of them by other companies (measured from a US location before any click).

  • 51 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) 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 agriframes.us, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 19 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Cookieyes Gdpr · Klaviyo Email Marketing Sms · Simprosys Google Shopping Feed · Helium Customer Fields · Goalify Free Shipping Goals · Microsoft Clarity · Assortion · Ta Labels Badges · Frontend · Smart Menu · stamped.io · webgains.com · gorgias.chat · shareasale.com · omnisnippet1.com · cloudfront.net · nfcube.com · 9gtb.com · Qikify

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on agriframes.us, including 17 speed issues, 3 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