Skip to content
Audit Complete

Results for https://www.capterra.com

Visit site
Netherlands Netherlands · Amsterdam Completed: Apr 7, 2026 20:25 UTC
Share card preview
Share on X Share on LinkedIn Share on Reddit Share on Hacker News Share via Email Download share image
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C78

Site Health

Score: 78 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

1

Content-Security-Policy header is missing

Security › Security Headers
2

HSTS header is missing

Security › Security Headers
3

No Content-Security-Policy header found

Security › Content Security Policy
4

No <main> landmark found

Accessibility › Landmark Structure
5

Cookie '__cf_bm' has no SameSite attribute

Security › Cookie Security
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.capterra.com)](https://beavercheck.com/results/f2d6927a-a76b-f7b6-e858-e3ef91f109ab)
<a href="https://beavercheck.com/results/f2d6927a-a76b-f7b6-e858-e3ef91f109ab"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.capterra.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.capterra.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

65
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
91
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
50
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

940 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.93 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

14.15 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.002

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.26 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

19.75 s

Detailed Report

Audit breakdown by category with detailed findings.

65

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

RequestCache TTLTransfer Size
www.capterra.com/favicon.ico86400.0 s2.5 KiB
/cdn-cgi/challenge-platform/h/b/d/9e8bbef2bfa2b950/177559...0.0 ms358 B
challenges.cloudflare.com/cdn-cgi/challenge-platform/h/b/cmg/10.0 ms208 B

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 761 ms
URLTime Spent
www.capterra.com/761 ms
www.capterra.com/0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Diagnostics

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

URLTotal CPU TimeScript EvaluationScript Parse
/cdn-cgi/challenge-platform/h/b/orchestrate/chl_page/v1?r...19.1 s18.8 s52 ms
Unattributable843 ms200 ms0.0 ms
www.capterra.com/148 ms16 ms4.5 ms
/turnstile/v0/b/625261456364/api.js?onload=OBvX9&render=e...105 ms60 ms13 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

CategoryTime Spent
Script Evaluation19.2 s
Other750 ms
Garbage Collection231 ms
Script Parsing & Compilation69 ms
Style & Layout54 ms
Rendering14 ms
Parse HTML & CSS12 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reasonFailure type
Pages that use WebXR are not currently eligible for back/forward cache.Actionable
Only pages with a status code of 2XX can be cached.Not actionable

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 501 KiB
●Avoid long main-thread tasks 20 long tasks found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 10 ms
●Server Backend Latencies 10 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 10 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid non-composited animations
91

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Best practices

Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Links are distinguishable without relying on color.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
96

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

SourceDescription
www.capterra.com/
Failed to load resource: the server responded with a status of 403 ()
●Uses HTTPS
●Avoids deprecated APIs
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Ensure proper origin isolation with COOP
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
50

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Crawling and Indexing

Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Blocking Directive Source
head > meta

Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.

To appear in search results, crawlers need access to your app.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid
●Document has a `<title>` element
●Links have descriptive text
●Links are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

73
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
87
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

715 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.02 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

455 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.29 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

5.46 s

Detailed Report

Audit breakdown by category with detailed findings.

73

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
AFAS Software div.flex > div.relative > div.inline-flex > img.h-full
/ProductLogo/be4b2d59-562c-4046-b042-e2119acab655.png41.1 KiB41.0 KiB
Zoho Projects div.flex > span.inline-flex > div.relative > img.h-full
/ProductLogo/90500a0b-eb4b-4bd0-a547-9b65bcc63bf5.png30.5 KiB30.5 KiB
div.mx-auto > div.relative > div.absolute > img.absolute div.mx-auto > div.relative > div.absolute > img.absolute
/assets-bx-capterra/_next/image?url=%2Fassets-bx-capterra...27.9 KiB20.9 KiB
Smartsheet div.flex > div.relative > div.inline-flex > img.h-full
/ProductLogo/9efb2a2f-43b2-4ebd-bf24-b9bb46bd93c6.jpeg19.2 KiB19.1 KiB
Barış Ergen div.inline-flex > div.relative > span.relative > img.aspect-square
/cdn/profile-images/linkedin/594523f20d9663a7010b928f261b...18.1 KiB18.1 KiB
Celoxis div.flex > div.relative > div.inline-flex > img.h-full
/ProductLogo/4e99765c-75ea-4a05-98ff-4d9a7288e686.png17.2 KiB17.0 KiB
Terence Zeng div.inline-flex > div.relative > span.relative > img.aspect-square
/cdn/profile-images/linkedin/4536654f5cd12286bff532ba1bef...14.9 KiB14.8 KiB
Rene Marquez div.inline-flex > div.relative > span.relative > img.aspect-square
/cdn/profile-images/linkedin/1c4a25549329feb775319e6c54eb...14.9 KiB14.8 KiB
Alan Varghese div.inline-flex > div.relative > span.relative > img.aspect-square
/cdn/profile-images/linkedin/ad163b0c84b4408b5f0a88164d08...14.2 KiB14.1 KiB
Aditya Raj Agrawal div.inline-flex > div.relative > span.relative > img.aspect-square
/cdn/profile-images/linkedin/1ed4dc2a4db802a36be3149909da...13.1 KiB13.0 KiB
John Mcgarr div.inline-flex > div.relative > span.relative > img.aspect-square
/cdn/profile-images/linkedin/e74411f5902ad3a0b9e47426b54d...12.9 KiB12.8 KiB
omogbeme astoji div.inline-flex > div.relative > span.relative > img.aspect-square
/cdn/profile-images/linkedin/ed730d5b7a04ad0ee17826635bf8...11.3 KiB11.2 KiB
Kevin Pérez div.inline-flex > div.relative > span.relative > img.aspect-square
/cdn/profile-images/linkedin/54ca96c953ea68932b81b01cdef9...9.4 KiB9.3 KiB
Joe Kwon div.inline-flex > div.relative > span.relative > img.aspect-square
/cdn/profile-images/linkedin/65869db6827b6a1784d1d99e8519...8.7 KiB8.6 KiB
David Farley div.inline-flex > div.relative > span.relative > img.aspect-square
/cdn/profile-images/linkedin/716cb84a0851d6048e8c087719c1...7.9 KiB7.8 KiB
Jay Bhatt div.inline-flex > div.relative > span.relative > img.aspect-square
/cdn/profile-images/linkedin/3d7fc24a4b4926649bf7656552c3...6.9 KiB6.8 KiB
Yeswanth A div.inline-flex > div.relative > span.relative > img.aspect-square
/cdn/profile-images/linkedin/eac4f1abe2dc385845a78571af03...6.3 KiB6.2 KiB
Eddy DeMelo div.inline-flex > div.relative > span.relative > img.aspect-square
/cdn/profile-images/linkedin/228f5772c851ed3cf381c26ead74...6.2 KiB6.1 KiB
MEENACHISUNDARAM MANOHAR div.inline-flex > div.relative > span.relative > img.aspect-square
/cdn/profile-images/linkedin/d0893ec25840c63ef028c246e2b1...5.8 KiB5.7 KiB

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

RequestCache TTLTransfer Size
cdn.cookielaw.org/scripttemplates/202403.2.0/otBannerSdk.js86400.0 s108.6 KiB
www.datadoghq-browser-agent.com/us1/v5/datadog-rum.js14400.0 s54.5 KiB
/cdn/profile-images/linkedin/193e485ea9246c461f9af9ba7ed5...0.0 ms20.8 KiB
/cdn/profile-images/linkedin/594523f20d9663a7010b928f261b...0.0 ms18.6 KiB
/cdn/profile-images/linkedin/9f06d153d688b9a7d4bb46aff8c0...0.0 ms16.1 KiB
/cdn/profile-images/linkedin/d82d1022fa19a59f3de5ecd22c2b...0.0 ms15.6 KiB
/cdn/profile-images/linkedin/4536654f5cd12286bff532ba1bef...0.0 ms15.4 KiB
/cdn/profile-images/linkedin/c61cff2bc5d02f576c5bf445f38c...0.0 ms15.4 KiB
/cdn/profile-images/linkedin/1c4a25549329feb775319e6c54eb...0.0 ms15.4 KiB
/cdn/profile-images/linkedin/ad163b0c84b4408b5f0a88164d08...0.0 ms14.7 KiB
/cdn/profile-images/linkedin/9b7d17662bdec1ce17b09361c5f0...0.0 ms14.6 KiB
/cdn/profile-images/linkedin/1ed4dc2a4db802a36be3149909da...0.0 ms13.6 KiB
/cdn/profile-images/linkedin/e74411f5902ad3a0b9e47426b54d...0.0 ms13.4 KiB
/cdn/profile-images/linkedin/f11585788474cf36fb87b47141f3...0.0 ms12.6 KiB
/cdn/profile-images/linkedin/bd3aaa1552ab94dc20cb1f6d22ac...0.0 ms12.4 KiB
/cdn/profile-images/linkedin/99e8719ca75a3af46730e9216c79...0.0 ms12.2 KiB
/cdn/profile-images/linkedin/8d568ddd40902de0ef17366b6882...0.0 ms11.9 KiB
/cdn/profile-images/linkedin/ed730d5b7a04ad0ee17826635bf8...0.0 ms11.8 KiB
/cdn/profile-images/linkedin/893b3f268557b0836a7323a0f405...0.0 ms11.8 KiB
/cdn/profile-images/linkedin/ecac3d9cfdf3bd7d87d10d7abd82...0.0 ms11.3 KiB
/cdn/profile-images/linkedin/27b3499198300101455e075d24f8...0.0 ms11.3 KiB
/cdn/profile-images/linkedin/fcaf3127fbf24a3affe93cf6b439...0.0 ms11.0 KiB
/cdn/profile-images/linkedin/84d3dd02fe978e6dcd8c558c7883...0.0 ms10.9 KiB
/cdn/profile-images/linkedin/590aa78945bbf74001a45932b2f2...0.0 ms10.8 KiB
/cdn/profile-images/linkedin/0ae5db82e8aff67217363661856e...0.0 ms10.5 KiB
/cdn/profile-images/linkedin/bba182e9db037fa0ec88bc2285e3...0.0 ms10.3 KiB
/cdn/profile-images/linkedin/57b2c883ce23bc763dcc61650319...0.0 ms10.0 KiB
/cdn/profile-images/linkedin/54ca96c953ea68932b81b01cdef9...0.0 ms9.8 KiB
/cdn/profile-images/linkedin/6efb3e32bb01ee68b20870696a39...0.0 ms9.4 KiB
/cdn/profile-images/linkedin/e2bd9a1a4efbcb509fd66048be9f...0.0 ms9.3 KiB
/cdn/profile-images/linkedin/6ddc598015ff825c4334df1900f1...0.0 ms9.2 KiB
/cdn/profile-images/linkedin/65869db6827b6a1784d1d99e8519...0.0 ms9.1 KiB
/cdn/profile-images/linkedin/e88450df428124693a9f7962f426...0.0 ms8.9 KiB
/cdn-cgi/challenge-platform/h/b/scripts/jsd/625261456364/...14400.0 s12.6 KiB
/cdn/profile-images/linkedin/37d5e3956fc6b66c122b02ff70ff...0.0 ms8.5 KiB
/cdn/profile-images/linkedin/716cb84a0851d6048e8c087719c1...0.0 ms8.3 KiB
/cdn/profile-images/linkedin/ff13f415e69a7c434f45b1443931...0.0 ms8.0 KiB
/cdn/profile-images/linkedin/3d7fc24a4b4926649bf7656552c3...0.0 ms7.4 KiB
/cdn/profile-images/linkedin/eac4f1abe2dc385845a78571af03...0.0 ms6.8 KiB
/cdn/profile-images/linkedin/228f5772c851ed3cf381c26ead74...0.0 ms6.7 KiB
/cdn/profile-images/linkedin/d0893ec25840c63ef028c246e2b1...0.0 ms6.3 KiB
/profile-images/linkedin/1dc2242cc9b9527e243745ec966910ee...0.0 ms5.9 KiB
/profile-images/linkedin/62a7ea73bfba3bf83d789b37aca30596...0.0 ms5.8 KiB
/profile-images/linkedin/905bed14a79d2a1bc841e0af65d6f902...0.0 ms5.6 KiB
/cdn/profile-images/linkedin/0e4f2ec925a1a1013f8c32681276...0.0 ms5.5 KiB
/profile-images/linkedin/3401daff7af6ae98ed99d678c18bf3d5...0.0 ms5.4 KiB
/profile-images/linkedin/1b8978f73bec234fc21164c749b3e426...0.0 ms5.1 KiB
/profile-images/linkedin/48cd31d89aaf2aa07acc5f13faa482af...0.0 ms4.4 KiB
/profile-images/linkedin/7d8a8d1dcb52bbbb54a0feb182499448...0.0 ms4.4 KiB
/profile-images/linkedin/f42b052010034b288cdb5f2b585c7595...0.0 ms4.2 KiB
/profile-images/linkedin/05d5a87e4b6c30269ce541ffca757ba1...0.0 ms3.9 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js86400.0 s9.1 KiB
/profile-images/linkedin/dc9f91c6b70595bf9520c07a5dd43e54...0.0 ms3.3 KiB
/cdn/profile-images/linkedin/f1ac6b607fea95a856f964d478aa...0.0 ms3.1 KiB
/profile-images/linkedin/817d80c07083805f5225f2efade641dc...0.0 ms2.5 KiB
/quem?authorization=pk_d7aff1b45c66427083cdd0457fcd4273&c...0.0 ms1.1 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Diagnostics

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

URLTotal CPU TimeScript EvaluationScript Parse
www.capterra.com/3.4 s95 ms15 ms
Unattributable624 ms59 ms0.0 ms
www.capterra.com/assets-bx-capterra/_next/static/chunks/0hgzfum-n2c7f.js521 ms442 ms14 ms
www.googletagmanager.com/gtm.js?id=GTM-NS6WSW4V269 ms213 ms27 ms
www.googletagmanager.com/gtag/js?id=DC-8036043&cx=c&gtm=4e6460237 ms218 ms13 ms
www.datadoghq-browser-agent.com/us1/v5/datadog-rum.js183 ms143 ms6.2 ms
/faas-modal-payload.js?formId=6HyOcTRcBkZLAc2QGex3tl144 ms116 ms19 ms
www.googletagmanager.com/gtag/js?id=G-M5DGBDHG2R&cx=c&gtm=4e6460117 ms81 ms20 ms
www.capterra.com/cdn-cgi/challenge-platform/scripts/jsd/main.js94 ms90 ms1.2 ms
www.googletagmanager.com/gtag/js?id=AW-1043250779&cx=c&gtm=4e646076 ms57 ms18 ms
www.googletagmanager.com/gtag/js?id=AW-653925177&cx=c&gtm=4e646074 ms57 ms16 ms
www.googletagmanager.com/gtag/js?id=AW-1072635088&cx=c&gtm=4e646074 ms53 ms20 ms
www.googletagmanager.com/gtag/js?id=AW-790705806&cx=c&gtm=4e646074 ms58 ms15 ms
www.capterra.com/assets-bx-capterra/_next/static/chunks/0vhyf.l7jg4yj.js69 ms63 ms6.0 ms
www.googletagmanager.com/gtag/js?id=AW-654961738&cx=c&gtm=4e646068 ms52 ms15 ms
cdn.cookielaw.org/scripttemplates/202403.2.0/otBannerSdk.js59 ms26 ms19 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

CategoryTime Spent
Other2.2 s
Script Evaluation1.9 s
Rendering1.0 s
Style & Layout705 ms
Script Parsing & Compilation295 ms
Garbage Collection119 ms
Parse HTML & CSS87 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 0.0 ms 690.3 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtm.js?id=GTM-NS6WSW4V184.0 KiB70.4 KiB
www.googletagmanager.com/gtag/js?id=G-M5DGBDHG2R&cx=c&gtm=4e6460170.6 KiB67.4 KiB
cdn.cookielaw.org/scripttemplates/202403.2.0/otBannerSdk.js108.4 KiB66.2 KiB
www.googletagmanager.com/gtag/js?id=AW-654961738&cx=c&gtm=4e6460143.4 KiB64.7 KiB
www.googletagmanager.com/gtag/js?id=AW-1043250779&cx=c&gtm=4e6460145.3 KiB64.4 KiB
www.googletagmanager.com/gtag/js?id=AW-1072635088&cx=c&gtm=4e6460133.3 KiB63.9 KiB
www.googletagmanager.com/gtag/js?id=AW-653925177&cx=c&gtm=4e6460133.4 KiB63.9 KiB
www.googletagmanager.com/gtag/js?id=AW-790705806&cx=c&gtm=4e6460133.4 KiB63.5 KiB
www.googletagmanager.com/gtag/js?id=DC-8036043&cx=c&gtm=4e6460129.3 KiB58.9 KiB
www.capterra.com/assets-bx-capterra/_next/static/chunks/08gvlhbk0v~gq.js72.5 KiB54.2 KiB
www.datadoghq-browser-agent.com/us1/v5/datadog-rum.js54.1 KiB28.8 KiB
www.capterra.com/assets-bx-capterra/_next/static/chunks/0hgzfum-n2c7f.js72.0 KiB24.0 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URLTransfer Size
www.googletagmanager.com/gtm.js?id=GTM-NS6WSW4V184.4 KiB
www.googletagmanager.com/gtag/js?id=G-M5DGBDHG2R&cx=c&gtm=4e6460170.6 KiB
www.googletagmanager.com/gtag/js?id=AW-1043250779&cx=c&gtm=4e6460145.4 KiB
www.googletagmanager.com/gtag/js?id=AW-654961738&cx=c&gtm=4e6460143.5 KiB
www.googletagmanager.com/gtag/js?id=AW-790705806&cx=c&gtm=4e6460133.5 KiB
www.googletagmanager.com/gtag/js?id=AW-653925177&cx=c&gtm=4e6460133.4 KiB
www.googletagmanager.com/gtag/js?id=AW-1072635088&cx=c&gtm=4e6460133.4 KiB
www.googletagmanager.com/gtag/js?id=DC-8036043&cx=c&gtm=4e6460129.3 KiB
cdn.cookielaw.org/scripttemplates/202403.2.0/otBannerSdk.js108.6 KiB
/modal/6HyOcTRcBkZLAc2QGex3tl?formId=6HyOcTRcBkZLAc2QGex3tl82.3 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●LCP request discovery
●Modern HTTP
●Network dependency tree
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●User Timing marks and measures 9 user timings
●Avoid long main-thread tasks 14 long tasks found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 100 ms
●Server Backend Latencies 400 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 10 ms
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
87

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

When a `progressbar` element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label `progressbar` elements.

Failing Elements
div.flex > div.flex > div.flex-1 > div.relative div.flex > div.flex > div.flex-1 > div.relative
div.flex > div.flex > div.flex-1 > div.relative div.flex > div.flex > div.flex-1 > div.relative
div.flex > div.flex > div.flex-1 > div.relative div.flex > div.flex > div.flex-1 > div.relative
div.flex > div.flex > div.flex-1 > div.relative div.flex > div.flex > div.flex-1 > div.relative
div.flex > div.flex > div.flex-1 > div.relative div.flex > div.flex > div.flex-1 > div.relative
div.flex > div.flex > div.flex-1 > div.relative div.flex > div.flex > div.flex-1 > div.relative
div.flex > div.flex > div.flex-1 > div.relative div.flex > div.flex > div.flex-1 > div.relative
div.flex > div.flex > div.flex-1 > div.relative div.flex > div.flex > div.flex-1 > div.relative
div.flex > div.flex > div.flex-1 > div.relative div.flex > div.flex > div.flex-1 > div.relative
div.flex > div.flex > div.flex-1 > div.relative div.flex > div.flex > div.flex-1 > div.relative
div.flex > div.flex > div.flex-1 > div.relative div.flex > div.flex > div.flex-1 > div.relative
div.flex > div.flex > div.flex-1 > div.relative div.flex > div.flex > div.flex-1 > div.relative
div.flex > div.flex > div.flex-1 > div.relative div.flex > div.flex > div.flex-1 > div.relative
div.flex > div.flex > div.flex-1 > div.relative div.flex > div.flex > div.flex-1 > div.relative
div.flex > div.flex > div.flex-1 > div.relative div.flex > div.flex > div.flex-1 > div.relative
div.flex > div.flex > div.flex-1 > div.relative div.flex > div.flex > div.flex-1 > div.relative

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
Accept All Cookies div#onetrust-button-group-parent > div#onetrust-button-group > div.banner-actions-container > button#onetrust-accept-btn-handler

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Failing Elements
head > meta head > meta

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Failing Elements
Performance Management System div.px-3 > ul.list-disc > li > a.w-fit
Human Resources div.px-3 > ul.list-disc > li > a.w-fit
Employee Scheduling div.px-3 > ul.list-disc > li > a.w-fit
Payroll div.px-3 > ul.list-disc > li > a.w-fit
Applicant Tracking div.px-3 > ul.list-disc > li > a.w-fit
Time Clock div.px-3 > ul.list-disc > li > a.w-fit
Recruiting div.px-3 > ul.list-disc > li > a.w-fit
Employee Engagement div.px-3 > ul.list-disc > li > a.w-fit
Employee Recognition div.px-3 > ul.list-disc > li > a.w-fit

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Failing Elements
Visit Website div.flex > div.grid > buyer-intent-click > button.inline-flex
Visit Website div.flex > div.grid > buyer-intent-click > button.inline-flex
Visit Website div.flex > div.grid > buyer-intent-click > button.inline-flex
Visit Website div.flex > div.grid > buyer-intent-click > button.inline-flex
Visit Website div.flex > div.grid > buyer-intent-click > button.inline-flex
Visit Website div.flex > div.grid > buyer-intent-click > button.inline-flex
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
77

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
div.mx-auto > div.relative > div.absolute > img.absolute div.mx-auto > div.relative > div.absolute > img.absolute
/assets-bx-capterra/_next/image?url=%2Fassets-bx-capterra...1876 x 504 (3.72)3840 x 979 (3.92)
div.mx-auto > div.flex > div.relative > img.absolute div.mx-auto > div.flex > div.relative > img.absolute
/assets-bx-capterra/_next/image?url=%2Fassets-bx-capterra...1118 x 776 (1.44)750 x 500 (1.50)

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Deprecation / WarningSource
SharedStorage
www.capterra.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
www.capterra.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge
www.capterra.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
●Uses HTTPS
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No browser errors logged to the console
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Detected JavaScript libraries
100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback