Website review, no card needed
collaborativeperks.com website review
Visit site (opens in a new tab)Reviewed 11 November 202625 issues · 72 checks
This review found 25 issues worth fixing on collaborativeperks.com, 6 of them high impact, across 72 checks. The most urgent: 168 text elements with low contrast. 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
87BClosest competitors among reviewed websites
Compare side by sideOne 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
Avoid multiple page redirects
863 msThe page goes through 1 redirect before it starts loading, costing about 863 ms. Link and advertise the final URL directly.
Render-blocking requests
700 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 700 ms.
1,772 HTML elements
The page has 1,772 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
unsplash.com adds 0 ms
0 msunsplash.com costs a phone 0 ms of main-thread work and 521 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.
Use efficient cache lifetimes
221 KiB4 files are served with short cache lifetimes, so returning visitors download them again (221 KiB).
1 long task on the main thread
1 long task block the main thread while loading, the longest for 146 ms. During a long task the page ignores taps.
2 third-party services on the page
2 third-party services load with your homepage (Google Fonts and unsplash.com), adding 639 KiB and 0 ms of main-thread time.
Minify CSS
21 KiB21 KiB could be saved by minifying CSS.
Reduce unused CSS
16 KiBAbout 16 KiB of CSS is downloaded but never applied on this page.
Improve image delivery
10 KiB2 images could be 10 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
3 checks passed
Mobile performance score: 94
94/100Your mobile performance score is 94. 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, 8 ms of it running JavaScript. That is comfortably low.
Server response: 119 ms
119 msYour server sent the HTML in 119 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 4.6 s
4.6 sVisually, the page fills in at 4.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
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.
4 checks passed
Largest Contentful Paint: 2.1 s
2.1 sYour largest element renders in 2.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “A turnkey HR portal SaaS with 15 on-demand modules: employe…”.
Time to Interactive: 2.1 s
2.1 sThe page is fully interactive after 2.1 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
About 0.3 g of CO₂ per visit
0.26 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.26 g of CO₂e: 31.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 934 KiB in 45 requests
934 KiBYour homepage downloads 934 KiB in 45 requests on a phone: images 742 KiB (39), fonts 116 KiB (3) and HTML 73 KiB (2). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
168 text elements with low contrast
168 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (11 elements)
Scrollable region must have keyboard access: 11 elements on the page fail this check, rated serious by axe-core.
Links look like plain text
3 links inside paragraphs rely on colour alone to stand out.
All page content should be contained by landmarks (63 elements)
All page content should be contained by landmarks: 63 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (4 elements)
Heading levels should only increase by one: 4 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one main landmark (1 element)
Document should not have more than one main 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.
1 checks passed
32 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (190 characters)
Your meta description is 190 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
8 internal links, 0 external
The homepage links to 8 pages on collaborativeperks.com and 0 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Collaborative Perks”.
Title: 56 characters
Your title is a healthy 56 characters: “Collaborative Perks — HR Portal & Employee Wellness Site”.
Canonical URL set
The canonical URL is https://www.collaborativeperks.com/en/.
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.collaborativeperks.com/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
1%A phone browser shows 3,330 words, but the HTML your server sends has only 19. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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://collaborativeperks.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.
1 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.
Other pages
8 links to non-canonical URLs
Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://collaborativeperks.com/en/index.html, whose canonical is https://collaborativeperks.com/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
8 internal pages checked
We fetched 8 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 8 pages we checked loaded without an error.
Every page has a meta description
All 8 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 8 pages that loaded have a <title>.
Best practices
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 404 ()”.
2 checks passed
Tap targets are thumb-sized
5 of 5 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 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 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 3,330 words of copy
The homepage carries about 3,330 words of visible text.
1 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book a demo →”.
Privacy and tracking
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.
3 other companies contacted
Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 collaborativeperks.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- AWS
Hiring
- Hiring
- 3 open roles
- Job board
- careers page
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on collaborativeperks.com, including 6 speed issues, 4 SEO issues 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.