Website review, no card needed

fumigationzone.com logo

fumigationzone.com website review

Visit site (opens in a new tab)Reviewed 22 November 202627 issues · 86 checks

This review found 27 issues worth fixing on fumigationzone.com, 4 of them high impact, across 86 checks. The most urgent: fails Core Web Vitals for real visitors. 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
5.7 s2.3 sMay 30Nov 142.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20264.6 s
Jun 6, 20265.1 s
Jun 13, 20265.2 s
Jun 20, 20265.3 s
Jun 27, 20264.8 s
Jul 4, 20263.9 s
Jul 11, 20263.2 s
Jul 18, 20262.9 s
Jul 25, 20263.1 s
Aug 1, 20263.1 s
Aug 8, 20262.9 s
Aug 15, 20263.2 s
Aug 22, 20263.4 s
Aug 29, 20263.6 s
Sep 5, 20263.8 s
Sep 12, 20264.1 s
Sep 19, 20263.9 s
Sep 26, 20263.7 s
Oct 3, 20263.5 s
Oct 10, 20263.1 s
Oct 17, 20263.1 s
Oct 24, 20263.3 s
Oct 31, 20263.1 s
Nov 7, 20262.9 s
Nov 14, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
239 ms80 msMay 30Nov 14162 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026173 ms
Jun 6, 2026187 ms
Jun 13, 2026189 ms
Jun 20, 2026193 ms
Jun 27, 2026215 ms
Jul 4, 2026209 ms
Jul 11, 2026200 ms
Jul 18, 2026200 ms
Jul 25, 2026221 ms
Aug 1, 2026184 ms
Aug 8, 2026119 ms
Aug 15, 2026101 ms
Aug 22, 2026101 ms
Aug 29, 2026105 ms
Sep 5, 2026110 ms
Sep 12, 2026105 ms
Sep 19, 202698 ms
Sep 26, 202698 ms
Oct 3, 2026102 ms
Oct 10, 2026104 ms
Oct 17, 2026109 ms
Oct 24, 2026164 ms
Oct 31, 2026159 ms
Nov 7, 2026158 ms
Nov 14, 2026162 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 fumigationzone.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix90
  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and Clarity and others), adding 1.4 MB and 801 ms of main-thread time.

  • Reduce unused JavaScript

    573 KiB

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

  • Google Tag Manager adds 374 ms

    374 ms

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

  • Google CDN adds 268 ms

    268 ms

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

  • Main-thread work: 2.3 s

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

  • 11 long tasks on the main thread

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

  • Reduce unused CSS

    55 KiB

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

  • Font display

    50 ms

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

  • Improve image delivery

    30 KiB

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

  • Use efficient cache lifetimes

    22 KiB

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

  • Legacy JavaScript

    12 KiB

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

2 checks passed
  • Mobile performance score: 90

    90/100

    Your mobile performance score is 90. That is in Google's “good” band (90 and up).

  • Server response: 34 ms

    34 ms

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

Core Web Vitals

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

  • Time to Interactive: 14.8 s

    14.8 s

    The page becomes fully interactive after 14.8 s. Good is under 3.8 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.7 s

    1.7 s

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

  • Total Blocking Time: 281 ms

    281 ms

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

  • Largest Contentful Paint: 2.9 s

    2.9 s

    Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Experts in Commercial Pest Solutions “We have built our bra…”.

7 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Tap response (INP) got 11% faster for real visitors

    -11%

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

  • Largest content (LCP) got 43% faster for real visitors

    -43%

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Speed Index: 2.2 s

    2.2 s

    Visually, the page fills in at 2.2 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.2 MB in 68 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 68 requests on a phone: scripts 1.4 MB (21), other files 362 KiB (15) and fonts 267 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.63 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

7 to fixGoogle 8792
  • 6 text elements with low contrast

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

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

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

  • Zoom is disabled

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

  • 2 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (6 elements)

    Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 31 images in the HTML carry an alt attribute.

  • 45 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: 45 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 8584
  • Title is short (15 characters)

    Your title is only 15 characters: “Home - FSS Inc.”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 40 links crawlers can't follow

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

  • 7 H1 headlines

    There are 7 <h1> headlines (“Experts in Commercial Pest Solutions”, “Industries We Serve” and “Protecting the Food Supply with Proven Pest Manag…”). One clear main headline is easier for people and search engines.

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

  • 130 internal links, 30 external

    The homepage links to 130 pages on fumigationzone.com and 30 external pages.

6 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Fumigation Service & Supply (FSS): structural, grain & export fumigation, IPM and microbial control for food facilities…”.

  • Canonical URL set

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

  • Structured data in place

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

  • 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://fsszone.com/sitemap.xml.

AI search readiness

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

    Your Organization JSON-LD is missing sameAs (social profiles), description 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://fsszone.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.

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

  • Text is in the HTML

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

Other pages

1 to fix98
  • 2 pages share a meta description

    https://fsszone.com/contact and https://fsszone.com/food-processing use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

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

Best practices

1 to fixGoogle 9684
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=134618828&tm=gtm002&Ver=2&mid=7043bfb4-8ce6-43b7-89ae-2772cefc3d47&bo=1&sid=083a7720e69e11f1881385de336c7fbf&vid=083a5de0e69e11f180e3ff385e969449&vids=1&msclkid=N&pi=9.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    12 of 14 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

    The homepage carries about 683 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: “Shop” and “Contact”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact” and “Learn More”.

  • 2 short forms

    2 short forms (7 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 23 testimonial or review blocks and 27 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 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
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Ads and Microsoft Clarity (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.

  • 11 cookies set on arrival

    11

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

  • 22 other companies contacted

    Loading the homepage contacts 22 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 fumigationzone.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
OVHcloud

Company

Headquarters
Westfield

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on fumigationzone.com, including 11 speed issues and 4 SEO 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