Website review, no card needed
staffany.com website review
Visit site (opens in a new tab)Reviewed 25 October 202647 issues · 92 checks
This review found 47 issues worth fixing on staffany.com, 18 of them high impact, across 92 checks. The most urgent: use efficient cache lifetimes. 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
67DClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.1 s |
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 260 ms |
| May 9, 2026 | 263 ms |
| May 16, 2026 | 244 ms |
| May 23, 2026 | 236 ms |
| May 30, 2026 | 260 ms |
| Jun 6, 2026 | 261 ms |
| Jun 13, 2026 | 251 ms |
| Jun 20, 2026 | 240 ms |
| Jun 27, 2026 | 231 ms |
| Jul 4, 2026 | 236 ms |
| Jul 11, 2026 | 242 ms |
| Jul 18, 2026 | 259 ms |
| Jul 25, 2026 | 253 ms |
| Aug 1, 2026 | 250 ms |
| Aug 8, 2026 | 258 ms |
| Aug 15, 2026 | 249 ms |
| Aug 22, 2026 | 248 ms |
| Aug 29, 2026 | 245 ms |
| Sep 5, 2026 | 249 ms |
| Sep 12, 2026 | 271 ms |
| Sep 19, 2026 | 284 ms |
| Sep 26, 2026 | 289 ms |
| Oct 3, 2026 | 275 ms |
| Oct 10, 2026 | 270 ms |
| Oct 17, 2026 | 267 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
1.7 s
3.4 s
5.2 s
6.9 s
8.6 s
10.3 s
12.0 s
13.8 s
Speed
Use efficient cache lifetimes
5.2 s · 1.9 MB119 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).
Reduce unused JavaScript
2.5 s · 4.2 MBAbout 4.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.
Google CDN adds 2.5 s
2.5 sGoogle CDN costs a phone 2.5 s of main-thread work and 4.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
1.8 s49 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Main-thread work: 13.2 s
A phone's processor spends 13.2 s on main-thread work while loading, 8.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 20
20/100Your mobile performance score is 20 (desktop: 27). 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 CDN, Google Tag Manager and Hubspot and others), adding 7.7 MB and 5.2 s of main-thread time.
Google Tag Manager adds 724 ms
724 msGoogle Tag Manager costs a phone 724 ms of main-thread work and 890 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.
Hubspot adds 719 ms
719 msHubspot costs a phone 719 ms of main-thread work and 614 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.
Reduce unused CSS
600 ms · 105 KiBAbout 105 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
hsappstatic.net adds 428 ms
428 mshsappstatic.net costs a phone 428 ms of main-thread work and 698 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 452 ms. During a long task the page ignores taps.
Facebook adds 318 ms
318 msFacebook costs a phone 318 ms of main-thread work and 292 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
264 KiB7 images could be 264 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2,065 HTML elements
The page has 2,065 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
26 KiBPolyfills for old browsers add 26 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.
1 checks passed
Server response: 389 ms
389 msYour server sent the HTML in 389 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: 13.9 s
13.9 sYour largest element takes 13.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Play Video”.
Speed Index: 20.3 s
20.3 sVisually, the page fills in at 20.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 58.2 s
58.2 sThe page becomes fully interactive after 58.2 s. Good is under 3.8 s.
Total Blocking Time: 2.9 s
2.9 sScripts block taps and scrolling for 2.9 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Real-user INP: 270 ms
270 msReal visitors wait 270 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.14
0.14For real visitors the layout shifts by 0.14 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.181
0.181The layout shifts by 0.181 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 260 ms to 267 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 581 ms
581 msReal visitors wait 581 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 12.0 MB in 288 requests
12.0 MBYour homepage downloads 12.0 MB in 288 requests on a phone: scripts 7.1 MB (98), other files 2.5 MB (52) and fonts 912 KiB (25). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
94 KiB2 images are downloaded at several times the size a phone draws them, for example 2.png at 512 px wide, shown at 110 px. Resized copies would save about 94 KiB.
4 images in older formats
4 images (250 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 3.4 g of CO₂ per visit
3.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.39 g of CO₂e: 407.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Unlabelled dropdowns
1 dropdown has no label.
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (3 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail this check, rated moderate 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.
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.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 59 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 63 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 11 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 3 problems
Structured data found (FAQPage, Organization, WebPage and WebSite) but with 3 problems, for example “Organization: sameAs is an empty list”.
12 links crawlers can't follow
12 links have no real href, so search engines can't follow them.
9 links with vague text
9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
142 internal links, 20 external
The homepage links to 142 pages on staffany.com and 20 external pages.
7 checks passed
Meta description: 101 characters
Your meta description is 101 characters: “Workforce management software connecting Operations and HR for seamless scheduling and time tracking.”.
One H1 headline
Your main headline reads: “The Ultimate Solution for F&B”.
Title: 57 characters
Your title is a healthy 57 characters: “Employee Workforce Management Software for F&B - StaffAny”.
Canonical URL set
The canonical URL is https://www.staffany.com/.
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.staffany.com/marketing-sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.staffany.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 description; sameAs (social profiles) and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,385 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a meta description
https://www.staffany.com/clubany and https://www.staffany.com/engageany 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://www.staffany.com/clubany, whose canonical is https://www.staffany.com/engageany. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://www.staffany.com/clubany and https://www.staffany.com/engageany have 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 29 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
3 small tap targets
3 of 11 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 752 words of copy
The homepage carries about 752 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: “Try for Free”.
22 calls to action
The homepage has 22 calls to action, for example “Learn more”, “Get Started” and “Pricing”.
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: 23 testimonial or review blocks, 1 customer or partner logo and 6 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and HubSpot.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 2 mores (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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
41 other companies contacted
Loading the homepage contacts 41 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 staffany.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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on staffany.com, including 24 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.