Website review, no card needed

fidelitybsg.com logo

fidelitybsg.com website review

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

This review found 35 issues worth fixing on fidelitybsg.com, 17 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. 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.5 s1.4 sMay 30Nov 142.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.1 s
Jun 20, 20262.0 s
Jun 27, 20261.9 s
Jul 4, 20262.1 s
Aug 22, 20261.7 s
Sep 12, 20261.9 s
Sep 19, 20261.7 s
Sep 26, 20261.6 s
Oct 3, 20261.5 s
Oct 10, 20261.8 s
Oct 31, 20262.4 s
Nov 7, 20262.0 s
Nov 14, 20262.1 s

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 fidelitybsg.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fidelitybsg.com at 0.7 s0.7 s
  2. fidelitybsg.com at 1.4 s1.4 s
  3. fidelitybsg.com at 2.1 s2.1 s
  4. fidelitybsg.com at 2.8 s2.8 s
  5. fidelitybsg.com at 3.5 s3.5 s
  6. fidelitybsg.com at 4.2 s4.2 s
  7. fidelitybsg.com at 4.9 s4.9 s
  8. fidelitybsg.com at 5.7 s5.7 s

Speed

7 to fix63
  • Use efficient cache lifetimes

    3.8 s · 12.0 MB

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

  • Render-blocking requests

    2.4 s

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

  • Reduce unused CSS

    1.1 s · 236 KiB

    About 236 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Reduce unused JavaScript

    1.1 s · 222 KiB

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

  • Improve image delivery

    2.9 MB

    9 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 63

    63/100

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

  • Font display

    400 ms

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, StatCounter and Google Fonts and others), adding 213 KiB and 106 ms of main-thread time.

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 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
  • Main-thread work: 1.9 s

    A phone's processor spends 1.9 s on main-thread work while loading, 881 ms of it running JavaScript. That is comfortably low.

  • Server response: 63 ms

    63 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 7.6 s

    7.6 s

    Your largest element takes 7.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 7.6 s

    7.6 s

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

  • Time to Interactive: 9.1 s

    9.1 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Real-user TTFB: 911 ms

    911 ms

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

  • 32 images without width and height

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

  • 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 2.0 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 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 CLS: 0.00

    0.00

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 12 ms

    12 ms

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

Images and page weight

5 to fix18
  • Page weight: 12.2 MB in 80 requests

    12.2 MB

    Your homepage downloads 12.2 MB in 80 requests on a phone: media 6.6 MB (2), images 4.5 MB (48) and scripts 569 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    2_FBSG_Homepage_FlagImage_V2.png weighs 1.5 MB. On a phone connection a single image that size takes seconds.

  • 5 images far larger than shown

    1.5 MB

    5 images are downloaded at several times the size a phone draws them, for example 2_FBSG_Homepage_FlagImage_V2.png at 2,680 px wide, shown at 375 px. Resized copies would save about 1.5 MB.

  • 5 images in older formats

    5 images (2.6 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.

  • 4 images below the first screen load straight away

    4 images further down the page (1.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.5 g of CO₂ per visit

    3.46 g

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

Accessibility

7 to fixGoogle 9190
  • 32 tap targets too small

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

  • 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 (17 elements)

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails 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 form field without a label

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

2 checks passed
  • Every image has alt text

    All 48 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 6 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 9288
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 2 links crawlers can't follow

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

  • 64 internal links, 5 external

    The homepage links to 64 pages on fidelitybsg.com and 5 external pages.

7 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “Fidelity Building Services Group is one of the nation’s leading providers of HVAC/Mechanical Services, Building Automat…”.

  • Title: 32 characters

    Your title is a healthy 32 characters: “Fidelity Building Services Group”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage 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://fidelitybsg.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://fidelitybsg.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: 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 (203 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 1 page slow to respond

    https://fidelitybsg.com/contact took over 3 s to send its HTML from our server.

  • 8 internal pages checked

    We fetched 8 pages linked from your homepage and read each the way a search engine does.

7 checks passed
  • Linked pages load

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

Best practices

2 to fixGoogle 9687
  • 2 small tap targets

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

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix67
  • 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.

  • No social proof

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

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

  • Only about 157 words

    The homepage has only about 157 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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

5 checks passed
  • 2 calls to action

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

  • 1 short form

    A short form (1 field at most) is 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.

  • Phone number on the homepage

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

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.

  • 3 cookies set on arrival

    3

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

  • 6 other companies contacted

    Loading the homepage contacts 6 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 fidelitybsg.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

Company

Employees
4,152

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 fidelitybsg.com, including 14 speed issues, 2 SEO issues and 4 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