Website review, no card needed
fluencetech.com website review
Visit site (opens in a new tab)Reviewed 20 October 202631 issues · 83 checks
This review found 31 issues worth fixing on fluencetech.com, 13 of them high impact, across 83 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 16.9 s |
| May 9, 2026 | 16.9 s |
| May 16, 2026 | 17.4 s |
| May 23, 2026 | 18.1 s |
| May 30, 2026 | 18.8 s |
| Jun 6, 2026 | 19.5 s |
| Jun 13, 2026 | 17.9 s |
| Jun 20, 2026 | 16.0 s |
| Jun 27, 2026 | 14.6 s |
| Jul 4, 2026 | 14.0 s |
| Jul 11, 2026 | 14.9 s |
| Jul 18, 2026 | 16.5 s |
| Jul 25, 2026 | 17.1 s |
| Aug 1, 2026 | 15.7 s |
| Aug 8, 2026 | 14.4 s |
| Aug 15, 2026 | 12.7 s |
| Aug 22, 2026 | 10.6 s |
| Aug 29, 2026 | 6.6 s |
| Sep 5, 2026 | 6.4 s |
| Sep 12, 2026 | 6.4 s |
| Sep 19, 2026 | 6.3 s |
| Sep 26, 2026 | 5.8 s |
| Oct 3, 2026 | 5.3 s |
| Oct 10, 2026 | 4.9 s |
| Oct 17, 2026 | 4.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 460 ms |
| May 9, 2026 | 472 ms |
| May 16, 2026 | 510 ms |
| May 23, 2026 | 544 ms |
| May 30, 2026 | 563 ms |
| Jun 6, 2026 | 591 ms |
| Jun 13, 2026 | 571 ms |
| Jun 20, 2026 | 563 ms |
| Jun 27, 2026 | 529 ms |
| Jul 4, 2026 | 540 ms |
| Jul 11, 2026 | 590 ms |
| Jul 18, 2026 | 645 ms |
| Jul 25, 2026 | 691 ms |
| Aug 1, 2026 | 645 ms |
| Aug 8, 2026 | 608 ms |
| Aug 15, 2026 | 547 ms |
| Aug 22, 2026 | 493 ms |
| Aug 29, 2026 | 464 ms |
| Sep 5, 2026 | 462 ms |
| Sep 12, 2026 | 455 ms |
| Sep 19, 2026 | 443 ms |
| Sep 26, 2026 | 368 ms |
| Oct 3, 2026 | 297 ms |
| Oct 10, 2026 | 245 ms |
| Oct 17, 2026 | 204 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
How it loaded on a phone
0.4 s
0.8 s
1.2 s
1.6 s
2.0 s
2.3 s
2.7 s
3.1 s
Speed
Render-blocking requests
2.8 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.
Use efficient cache lifetimes
1.4 s · 195 KiB16 files are served with short cache lifetimes, so returning visitors download them again (195 KiB).
Mobile performance score: 40
40/100Your mobile performance score is 40 (desktop: 75). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused JavaScript
450 ms · 86 KiBAbout 86 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Legacy JavaScript
350 ms · 34 KiBPolyfills for old browsers add 34 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 880 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,448 HTML elements
The page has 2,448 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
7 third-party services on the page
7 third-party services load with your homepage (bc0a.com, Optanon and Adobe Tag Manager and others), adding 514 KiB and 327 ms of main-thread time.
Reduce unused CSS
150 ms · 58 KiBAbout 58 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 94 ms. During a long task the page ignores taps.
Improve image delivery
32 KiB2 images could be 32 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Phones get a much slower page than desktops
Desktop scores 75 but mobile only 40. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 12.4 s
12.4 sYour largest element takes 12.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Soft gradient background with warm peach tones blending int…”.
First Contentful Paint: 5.3 s
5.3 sThe first text or image appears after 5.3 s on a phone. Good is under 1.8 s.
Time to Interactive: 12.5 s
12.5 sThe page becomes fully interactive after 12.5 s. Good is under 3.8 s.
Speed Index: 8.0 s
8.0 sVisually, the page fills in at 8.0 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.38
0.38The layout shifts by 0.38 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user INP: 210 ms
210 msReal visitors wait 210 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.15
0.15For real visitors the layout shifts by 0.15 (75th percentile). Good is under 0.1.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
24 images without width and height
24 images have no width and height attributes, so the layout jumps as each one loads.
5 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user TTFB: 610 ms
610 msReal visitors wait 610 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 52% faster for real visitors
-52%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 460 ms to 204 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 72% faster for real visitors
-72%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 16.9 s to 4.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 45 ms
45 msScripts block the page for only 45 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.3 MB in 124 requests
4.3 MBYour homepage downloads 4.3 MB in 124 requests on a phone: images 2.4 MB (44), fonts 711 KiB (2) and other files 610 KiB (14). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 1.8 MB together. On a phone connection a single image that size takes seconds.
5 images far larger than shown
1.4 MB5 images are downloaded at several times the size a phone draws them, for example connected-dots-dark-blue-icon.svg at 150 px wide, shown at 24 px. Resized copies would save about 1.4 MB.
4 images below the first screen load straight away
4 images further down the page (306 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.22 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.22 g of CO₂e: 146.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h3 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (5 elements).
2 checks passed
Every image has alt text
All 81 images in the HTML carry an alt attribute.
47 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: 47 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
11 links with vague text
11 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
259 internal links, 19 external
The homepage links to 259 pages on fluencetech.com and 19 external pages.
8 checks passed
Meta description: 121 characters
Your meta description is 121 characters: “The scenario planning and analysis platform where AI, data, and planning converge to make the right decisions, right no…”.
One H1 headline
Your main headline reads: “The decision infrastructure for the Agentic Enterprise”.
Title: 57 characters
Your title is a healthy 57 characters: “Decision Infrastructure for Agentic Enterprises | Anaplan”.
Canonical URL set
The canonical URL is https://www.anaplan.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://www.anaplan.com/sitemap.xml.
AI search readiness
4 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, sameAs (social profiles) and contact details; logo and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,008 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.anaplan.com/llms.txt (3 KiB, 10 links), a plain-text guide to the site for AI tools.
Other pages
1 page without an H1
https://www.anaplan.com/request-demo has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 173 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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
5 small tap targets
5 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 634 words of copy
The homepage carries about 634 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: “Get a demo” and “Contact”.
22 calls to action
The homepage has 22 calls to action, for example “Contact”, “Get a demo” and “Contact Center Planning”.
Social proof on the page
Social proof on the homepage: 16 customer or partner logos and 33 trust badges.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Analytics (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
5 cookies set on arrival
5Opening the homepage sets 5 cookies (measured from a US location before any click).
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 fluencetech.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
Hiring
- Hiring
- 129 open roles
- Teams
- Engineering (23), Field Sales (18), Finance (13), Pre-Sales (12)
- Job board
- greenhouse
- Careers page
- www.anaplan.com/careers (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on fluencetech.com, including 17 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.