Website review, no card needed

fieldpiece.com logo

fieldpiece.com website review

Visit site (opens in a new tab)Reviewed 19 October 202657 issues · 98 checks

This review found 57 issues worth fixing on fieldpiece.com, 22 of them high impact, across 98 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 fieldpiece.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fieldpiece.com at 2.1 s2.1 s
  2. fieldpiece.com at 4.2 s4.2 s
  3. fieldpiece.com at 6.3 s6.3 s
  4. fieldpiece.com at 8.3 s8.3 s
  5. fieldpiece.com at 10.4 s10.4 s
  6. fieldpiece.com at 12.5 s12.5 s
  7. fieldpiece.com at 14.6 s14.6 s
  8. fieldpiece.com at 16.7 s16.7 s

Speed

15 to fix25
  • Reduce unused JavaScript

    3.3 s · 2.0 MB

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

  • Use efficient cache lifetimes

    1.4 s · 1.8 MB

    23 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).

  • Google Tag Manager adds 2.5 s

    2.5 s

    Google Tag Manager costs a phone 2.5 s of main-thread work and 526 KiB 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.

  • Google CDN adds 2.2 s

    2.2 s

    Google CDN costs a phone 2.2 s of main-thread work and 1.4 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.

  • Main-thread work: 17.5 s

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

  • YouTube adds 1.4 s

    1.4 s

    YouTube costs a phone 1.4 s of main-thread work and 991 KiB 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.

  • ClickDimensions adds 1.3 s

    1.3 s

    ClickDimensions costs a phone 1.3 s of main-thread work and 506 KiB 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.

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 25

    25/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and YouTube and others), adding 3.9 MB and 8.8 s of main-thread time.

  • Improve image delivery

    800 ms · 824 KiB

    6 images could be 824 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 1.2 s. During a long task the page ignores taps.

  • Reduce unused CSS

    540 ms · 223 KiB

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

  • Facebook adds 544 ms

    544 ms

    Facebook costs a phone 544 ms of main-thread work and 225 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.

  • Minify JavaScript

    300 ms · 48 KiB

    48 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    150 ms · 42 KiB

    Polyfills for old browsers add 42 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

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

    8 ms

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

Core Web Vitals

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

  • First Contentful Paint: 8.4 s

    8.4 s

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

  • Largest Contentful Paint: 13.1 s

    13.1 s

    Your largest element takes 13.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “TECH Rewards Earn Points. Get Swag. Learn More Are your too…”.

  • Total Blocking Time: 8.4 s

    8.4 s

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

  • Time to Interactive: 30.5 s

    30.5 s

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

  • Speed Index: 12.9 s

    12.9 s

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

  • Real-user CLS: 0.18

    0.18

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

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

    +26%

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

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

    +36%

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • 8 images without width and height

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

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: 176 ms

    176 ms

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

3 to fix60
  • Page weight: 6.1 MB in 145 requests

    6.1 MB

    Your homepage downloads 6.1 MB in 145 requests on a phone: scripts 3.9 MB (51), images 1.1 MB (26) and other files 379 KiB (52). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (1.1 MB) 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.

  • An image on the first screen is lazy-loaded

    A2L.png 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).

  • 1 image below the first screen load straight away

    1 image further down the page (177 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.7 g of CO₂ per visit

    1.73 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.73 g of CO₂e: 208.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

12 to fixGoogle 8184
  • 6 buttons without a name

    6 buttons have no accessible name, so screen readers announce just “button”.

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

  • Frames without titles

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

  • 33 images without alt text

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

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

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

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

  • 11 links without text

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

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

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

  • Elements marked as presentational should be consistently ignored (2 elements)

    Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

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

SEO

4 to fixGoogle 9283
  • Title is short (29 characters)

    Your title is only 29 characters: “HVAC Vacuum Pump | Fieldpiece”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 43 links with vague text

    43 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 4 H1 headlines

    There are 4 <h1> headlines (“New! Analog Gauge Sets”, “Refrigerant & Combustible Gas Leak Detector” and “TECH Rewards”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 165 internal links, 23 external

    The homepage links to 165 pages on fieldpiece.com and 23 external pages.

5 checks passed
  • Meta description: 109 characters

    Your meta description is 109 characters: “Check out Fieldpiece for all of your HVAC and HVACR needs! We look forward to working with you in the future.”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.fieldpiece.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://www.fieldpiece.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 (724 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix76
  • 6 pages share 3 titles

    https://www.fieldpiece.com/our-company and https://www.fieldpiece.com/about-fieldpiece all use the title “Industry Leading HVACR Tools - HVAC Gauges and more | Fieldpiece”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://www.fieldpiece.com/fr, https://www.fieldpiece.com/es, https://www.fieldpiece.com/testimonials, https://www.fieldpiece.com/success-stories and https://www.fieldpiece.com/careers have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://www.fieldpiece.com/our-company and https://www.fieldpiece.com/about-fieldpiece use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.fieldpiece.com/our-company, whose canonical is https://www.fieldpiece.com/about-fieldpiece. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 6 pages without an H1

    https://www.fieldpiece.com/fr, https://www.fieldpiece.com/es, https://www.fieldpiece.com/news-articles/category/blog, https://www.fieldpiece.com/news-articles/category/press-release, https://www.fieldpiece.com/news-articles/category/tech-article and https://www.fieldpiece.com/news-articles/category/videos have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.fieldpiece.com/news-articles/category/blog took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

4 to fixGoogle 6970
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97017015&tm=gtm002&Ver=2&mid=a38943eb-415a-4fc0-94dc-0db183e6ba98&bo=1&sid=c7c8c700cc0211f1abeb5df20ffc277d&vid=c7c8d930cc0211f18f75bf5b20c7982d&vids=1&msclkid=N&gtm_t.

  • 16 small tap targets

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

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “$ is not a function”.

  • 4 low-resolution images

    4 images are served at too low a resolution for sharp phone screens.

  • 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

1 to fix83
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

    The homepage carries about 419 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Merchandise Shop” and “Where to Buy”.

  • 19 calls to action

    The homepage has 19 calls to action, for example “Merchandise Shop”, “Where to Buy” and “Learn More”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 4 mores (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.

  • 27 cookies set on arrival

    27

    Opening the homepage sets 27 cookies, 1 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.

  • 31 other companies contacted

    Loading the homepage contacts 31 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 fieldpiece.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 57 issues on fieldpiece.com, including 26 speed issues, 4 SEO issues and 1 conversion gap. 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