Website review, no card needed

finesseforce.com logo

finesseforce.com website review

Visit site (opens in a new tab)Reviewed 11 November 202636 issues · 79 checks

This review found 36 issues worth fixing on finesseforce.com, 11 of them high impact, across 79 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

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

How it loaded on a phone

  1. finesseforce.com at 1.1 s1.1 s
  2. finesseforce.com at 2.1 s2.1 s
  3. finesseforce.com at 3.2 s3.2 s
  4. finesseforce.com at 4.3 s4.3 s
  5. finesseforce.com at 5.3 s5.3 s
  6. finesseforce.com at 6.4 s6.4 s
  7. finesseforce.com at 7.5 s7.5 s
  8. finesseforce.com at 8.5 s8.5 s

Speed

11 to fix52
  • Use efficient cache lifetimes

    3.8 s · 689 KiB

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

  • Reduce unused JavaScript

    1.8 s · 821 KiB

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

  • Render-blocking requests

    2.4 s

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

  • Improve image delivery

    1.5 s · 828 KiB

    4 images could be 828 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.

  • Main-thread work: 4.2 s

    A phone's processor spends 4.2 s on main-thread work while loading, 2.1 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 (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 2.0 MB and 970 ms of main-thread time.

  • Reduce unused CSS

    920 ms · 208 KiB

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

  • Mobile performance score: 52

    52/100

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

  • Google CDN adds 583 ms

    583 ms

    Google CDN costs a phone 583 ms of main-thread work and 743 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 Tag Manager adds 323 ms

    323 ms

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

  • WordPress adds 0 ms

    0 ms

    WordPress costs a phone 0 ms of main-thread work and 729 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.

  • Legacy JavaScript

    200 ms · 23 KiB

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

  • 15 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Minify CSS

    20 ms · 3 KiB

    3 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: 40 ms

    40 ms

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

Core Web Vitals

6 to fix54
  • Largest Contentful Paint: 13.4 s

    13.4 s

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

  • Time to Interactive: 21.3 s

    21.3 s

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

  • Speed Index: 9.0 s

    9.0 s

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

  • Total Blocking Time: 452 ms

    452 ms

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • 9 images without width and height

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

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

1 checks passed
  • Cumulative Layout Shift: 0.035

    0.035

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

Images and page weight

2 to fix63
  • Page weight: 4.1 MB in 101 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 101 requests on a phone: scripts 1.6 MB (39), images 1.1 MB (18) and fonts 679 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 2 images below the first screen load straight away

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

  • About 1.2 g of CO₂ per visit

    1.17 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9194
  • 9 text elements with low contrast

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

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 21 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 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9281
  • No H1 headline

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

  • Title is long (80 characters)

    Your title is 80 characters, so Google will cut it off around 60: “Fractional CMO Services for B2B | Strategic Marketing Leadership - Finesse Force”.

  • 3 links with vague text

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

  • 37 internal links, 3 external

    The homepage links to 37 pages on finesseforce.com and 3 external pages.

6 checks passed
  • Meta description: 117 characters

    Your meta description is 117 characters: “Finesse Force is your executive-level growth partner. We help B2B brands build authority and activate revenue growth.”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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://finesseforce.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://finesseforce.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: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

5 to fix76
  • 2 pages share a title

    https://finesseforce.com/fractional-cmo and https://finesseforce.com/fractional-CMO all use the title “Fractional CMO - Finesse Force”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://finesseforce.com/customers, https://finesseforce.com/contact, https://finesseforce.com/blog/category/product-marketing and https://finesseforce.com/blog/category/messaging have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://finesseforce.com/fractional-cmo and https://finesseforce.com/fractional-CMO use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://finesseforce.com/fractional-CMO, whose canonical is https://finesseforce.com/fractional-cmo. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 9 pages without an H1

    https://finesseforce.com/fractional-cmo, https://finesseforce.com/brand-communications, https://finesseforce.com/coaching, https://finesseforce.com/blog, https://finesseforce.com/contact and https://finesseforce.com/blog/category/fractional-cmo and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages with very little text

    https://finesseforce.com/customers, https://finesseforce.com/blog, https://finesseforce.com/contact, https://finesseforce.com/blog/category/fractional-cmo, https://finesseforce.com/blog/category/product-marketing and https://finesseforce.com/blog/category/messaging have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 14 internal pages checked

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

3 checks passed
  • Linked pages load

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

Best practices

2 to fixGoogle 9287
  • 2 small tap targets

    2 of 8 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: the server responded with a status of 400 ()”.

  • 2 low-resolution images

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 734 words of copy

    The homepage carries about 734 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: “Contact” and “Book a Strategy Call →”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact”, “Book a Strategy Call →” and “Learn more”.

  • 1 short form

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

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, 9 customer or partner logos and 16 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

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.

  • 4 cookies set on arrival

    4

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

  • 14 other companies contacted

    Loading the homepage contacts 14 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 finesseforce.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 | Google Tag Manager
Hosting
Oracle Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

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