Website review, no card needed
worldmanager.com website review
Visit site (opens in a new tab)Reviewed 21 November 202618 issues · 80 checks
This review found 18 issues worth fixing on worldmanager.com, 5 of them high impact, across 80 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
90AClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.8 s |
| Jun 13, 2026 | 3.9 s |
| Jun 20, 2026 | 3.9 s |
| Jun 27, 2026 | 4.1 s |
| Jul 4, 2026 | 4.4 s |
| Jul 11, 2026 | 4.8 s |
| Jul 18, 2026 | 5.2 s |
| Jul 25, 2026 | 5.4 s |
| Aug 1, 2026 | 5.5 s |
| Aug 8, 2026 | 5.4 s |
| Aug 15, 2026 | 5.3 s |
| Aug 22, 2026 | 5.0 s |
| Aug 29, 2026 | 4.5 s |
| Sep 5, 2026 | 4.4 s |
| Sep 12, 2026 | 3.9 s |
| Sep 19, 2026 | 3.7 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.8 s |
| Oct 31, 2026 | 2.8 s |
| Nov 7, 2026 | 2.9 s |
| Nov 14, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 144 ms |
| Jun 6, 2026 | 163 ms |
| Jun 13, 2026 | 176 ms |
| Jun 20, 2026 | 176 ms |
| Jun 27, 2026 | 183 ms |
| Jul 4, 2026 | 173 ms |
| Jul 11, 2026 | 163 ms |
| Jul 18, 2026 | 158 ms |
| Jul 25, 2026 | 160 ms |
| Aug 1, 2026 | 166 ms |
| Aug 8, 2026 | 173 ms |
| Aug 15, 2026 | 172 ms |
| Aug 22, 2026 | 171 ms |
| Aug 29, 2026 | 173 ms |
| Sep 5, 2026 | 178 ms |
| Sep 12, 2026 | 189 ms |
| Sep 19, 2026 | 177 ms |
| Sep 26, 2026 | 165 ms |
| Oct 3, 2026 | 127 ms |
| Oct 10, 2026 | 104 ms |
| Oct 17, 2026 | 104 ms |
| Oct 24, 2026 | 108 ms |
| Oct 31, 2026 | 112 ms |
| Nov 7, 2026 | 124 ms |
| Nov 14, 2026 | 126 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.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.1 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Use efficient cache lifetimes
300 ms · 65 KiB4 files are served with short cache lifetimes, so returning visitors download them again (65 KiB).
1,606 HTML elements
The page has 1,606 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
5 third-party services on the page
5 third-party services load with your homepage (Wistia, Cookiebot and Google Tag Manager and others), adding 519 KiB and 250 ms of main-thread time.
Reduce unused JavaScript
245 KiBAbout 245 KiB of JavaScript is downloaded but never used on this page.
Improve image delivery
193 KiB1 image could be 193 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 95 ms. During a long task the page ignores taps.
Reduce unused CSS
26 KiBAbout 26 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
10 KiB10 KiB could be saved by minifying JavaScript.
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.
3 checks passed
Mobile performance score: 97
97/100Your mobile performance score is 97. That is in Google's “good” band (90 and up).
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 290 ms of it running JavaScript. That is comfortably low.
Server response: 8 ms
8 msYour server sent the HTML in 8 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.
Real-user TTFB: 2.4 s
2.4 sReal visitors wait 2.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.0 s
3.0 sReal visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.
Time to Interactive: 6.4 s
6.4 sThe page becomes fully interactive after 6.4 s. Good is under 3.8 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
8 checks passed
Real-user INP: 124 ms
124 msReal visitors wait 124 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Tap response (INP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 144 ms to 126 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.7 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 2.0 s
2.0 sYour largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “FranConnect Training & Development helps multi-location bra…”.
Speed Index: 2.6 s
2.6 sVisually, the page fills in at 2.6 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0.044
0.044The layout barely moves while loading (CLS 0.044, good is under 0.1).
Total Blocking Time: 34 ms
34 msScripts block the page for only 34 ms while loading. Good is under 200 ms.
Images and page weight
1 image far larger than shown
152 KiB1 image is downloaded at several times the size a phone draws it, for example World-Manager-Elearning.png at 1,939 px wide, shown at 358 px. Resized copies would save about 152 KiB.
1 image below the first screen load straight away
1 image further down the page (219 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.3 g of CO₂ per visit
0.31 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.31 g of CO₂e: 37.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.1 MB in 41 requests
1.1 MBYour homepage downloads 1.1 MB in 41 requests on a phone: scripts 682 KiB (26), images 359 KiB (8) and HTML 48 KiB (2). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails 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 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.
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.
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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (11 elements).
2 checks passed
Every image has alt text
All 21 images in the HTML carry an alt attribute.
44 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: 44 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
180 internal links, 23 external
The homepage links to 180 pages on worldmanager.com and 23 external pages.
8 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “FranConnect’s Training & Development turns your goals into results -- building skills, ensuring compliance, and driving…”.
One H1 headline
Your main headline reads: “Train to Perform. Comply. Deliver.”.
Title: 55 characters
Your title is a healthy 55 characters: “Frontline Training & Development Software - FranConnect”.
Canonical URL set
The canonical URL is https://www.franconnect.com/platform-overview/training-and-development/.
Structured data in place
Structured data found: BreadcrumbList, Organization, SoftwareApplication, 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.franconnect.com/video-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: 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 (1,114 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.franconnect.com/llms.txt (152 KiB, 400 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 74 found) and read each the way a search engine does.
7 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.
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
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
9 of 11 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 710 words of copy
The homepage carries about 710 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Request a Demo”.
13 calls to action
The homepage has 13 calls to action, for example “Contact Us”, “Request a Demo” and “Best Practice Content Download”.
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 and 11 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 4 phone links and 4 email links.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
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.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 worldmanager.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
- Analytics
- Google Tag Manager
- Hosting
- AWS
Hiring
- Hiring
- 3 open roles
- Job board
- paylocity
Company
- Headquarters
- Sydney
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 18 issues on worldmanager.com, including 10 speed issues. 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.