Website review, no card needed

joinflo.com logo

joinflo.com website review

Visit site (opens in a new tab)Reviewed 17 November 202634 issues · 79 checks

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

Real-visitor load time (LCP)75th percentile, phones
3.5 s2.2 sJul 25Nov 142.4 s
Show as table
DateReal-visitor load time (LCP)
Jul 25, 20262.5 s
Aug 1, 20263.3 s
Aug 8, 20262.7 s
Aug 15, 20262.8 s
Aug 22, 20263.0 s
Aug 29, 20262.8 s
Sep 5, 20263.0 s
Sep 12, 20262.9 s
Sep 19, 20262.7 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 10, 20262.9 s
Oct 17, 20263.0 s
Oct 24, 20262.8 s
Oct 31, 20262.7 s
Nov 7, 20262.4 s
Nov 14, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
213 ms93 msAug 1Nov 14107 ms
Show as table
DateReal-visitor tap response (INP)
Aug 1, 2026163 ms
Aug 8, 2026179 ms
Aug 15, 2026197 ms
Aug 22, 2026199 ms
Aug 29, 2026181 ms
Sep 5, 2026177 ms
Sep 12, 2026180 ms
Sep 19, 2026175 ms
Sep 26, 2026172 ms
Oct 3, 2026165 ms
Oct 10, 2026161 ms
Oct 17, 2026154 ms
Oct 24, 2026143 ms
Oct 31, 2026127 ms
Nov 7, 2026112 ms
Nov 14, 2026107 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 joinflo.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. joinflo.com at 0.7 s0.7 s
  2. joinflo.com at 1.3 s1.3 s
  3. joinflo.com at 2.0 s2.0 s
  4. joinflo.com at 2.7 s2.7 s
  5. joinflo.com at 3.4 s3.4 s
  6. joinflo.com at 4.0 s4.0 s
  7. joinflo.com at 4.7 s4.7 s
  8. joinflo.com at 5.4 s5.4 s

Speed

12 to fix49
  • Reduce unused JavaScript

    6.8 s · 1.1 MB

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

  • Use efficient cache lifetimes

    5.5 s · 961 KiB

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

  • Render-blocking requests

    2.4 s

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

  • Mobile performance score: 49

    49/100

    Your mobile performance score is 49. 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, bestfreecdn.com and Osano CMP and others), adding 3.1 MB and 1.3 s of main-thread time.

  • Google Tag Manager adds 454 ms

    454 ms

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

  • Improve image delivery

    392 KiB

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

  • Reduce unused CSS

    320 ms · 60 KiB

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

  • bestfreecdn.com adds 277 ms

    277 ms

    bestfreecdn.com costs a phone 277 ms of main-thread work and 955 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.

  • 12 long tasks on the main thread

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

  • Main-thread work: 2.8 s

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

  • website-files.com adds 31 ms

    31 ms

    website-files.com costs a phone 31 ms of main-thread work and 1.1 MB 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.

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

    3 ms

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

Core Web Vitals

8 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: 20.5 s

    20.5 s

    Your largest element takes 20.5 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.9 s

    21.9 s

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

  • Total Blocking Time: 680 ms

    680 ms

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

  • Speed Index: 5.9 s

    5.9 s

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • 48 images without width and height

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

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 INP: 107 ms

    107 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user TTFB: 658 ms

    658 ms

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

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

    -36%

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

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

    -18%

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

  • Cumulative Layout Shift: 0.016

    0.016

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

Images and page weight

1 to fix85
  • Page weight: 3.5 MB in 115 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 115 requests on a phone: scripts 2.0 MB (34), fonts 741 KiB (24) and images 718 KiB (30). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (122 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.0 g of CO₂ per visit

    1.01 g

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

2 checks passed
  • 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

5 to fixGoogle 9193
  • 3 tap targets too small

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

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

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

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

    Document should not have more than one banner 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.

  • 2 links without text

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

2 checks passed
  • Every image has alt text

    All 139 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 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 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 10088
  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No XML sitemap

    No XML sitemap at https://www.joinflo.com/sitemap.xml, so Google discovers your pages only by following links.

  • 188 internal links, 28 external

    The homepage links to 188 pages on joinflo.com and 28 external pages.

5 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Flo connects law firms, law schools, and legal talent — with software for recruiting, performance management, career se…”.

  • One H1 headline

    Your main headline reads: “The Talent Platform for Legal”.

  • Title: 34 characters

    Your title is a healthy 34 characters: “Flo: The Talent Platform for Legal”.

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

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

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

Other pages

1 to fix95
  • 1 page without a meta description

    https://www.joinflo.com/products/flo-csm has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

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

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Webflow is not defined”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 372 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Request Demo”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Contact Us”, “Request Demo” and “Request a Demo”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, HubSpot and LinkedIn Insight.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight (measured from a US location before any click). A consent tool (Osano) 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, 7 of them by other companies (measured from a US location before any click).

  • 35 other companies contacted

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

1 checks passed
  • Consent tool: Osano

    A consent management tool (Osano) 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 joinflo.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
Webflow
Analytics
Google Analytics | Google Tag Manager
Hosting
Webflow

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on joinflo.com, including 20 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