Skip to content
Audit Complete

Results for https://www.g2.com

Visit site
Singapore Singapore · Singapore Completed: Apr 7, 2026 20:23 UTC

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)
D68

Site Health

Score: 68 / 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

Access-Control-Allow-Origin: * with credentials — critical misconfiguration

Security › CORS Configuration
2

Content-Security-Policy 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

113 HTTP requests — consider bundling or reducing

Performance › Page Weight Budget
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.g2.com)](https://beavercheck.com/results/684ff8ca-27e9-61a9-8bfc-839b0772e024)
<a href="https://beavercheck.com/results/684ff8ca-27e9-61a9-8bfc-839b0772e024"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.g2.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.g2.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.

29
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
75
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.
85
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.

7.03 s

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

8.66 s

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

2.71 s

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

0.031

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

7.03 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.54 s

Detailed Report

Audit breakdown by category with detailed findings.

29

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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-0-DIV
nodeLabel: div.background-header__body > div.background-header__image-container > div.position-relative > div.background-header__image
path: 1,HTML,1,BODY,6,DIV,1,DIV,1,DIV,0,DIV,7,DIV,0,DIV,0,DIV,0,DIV,1,DIV
selector: div.background-header__body > div.background-header__image-container > div.position-relative > div.background-header__image
snippet: <div class="background-header__image">

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
value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

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
Review screenshots div.paper-padding-x > div.grid-x > div.cell > img
/assets/homepage_reviews_screenshot-e3f43d8a1b2de15981f59...122.3 KiB89.9 KiB
G2 Profile screenshots div.paper-padding-x > div.grid-x > div.cell > img
/assets/profile_screenshots-a84b3e5b2d744fbcaafb601feb176...58.9 KiB43.2 KiB
Matthew Gardner div.text-normal > div.hide-for-xlarge > div.cell > img.mb-1
/assets/reviewer_image1-63f003a2437fdab1c5ab51e13f673b4f4...33.9 KiB31.8 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

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Estimated savings: 2.9 s 676.2 KiB

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

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 Evaluation7.3 s
Other1.7 s
Style & Layout808 ms
Script Parsing & Compilation710 ms
Parse HTML & CSS336 ms
Garbage Collection155 ms
Rendering116 ms

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

URL
G2 Profile screenshots div.paper-padding-x > div.grid-x > div.cell > img
/assets/profile_screenshots-a84b3e5b2d744fbcaafb601feb176...
Review screenshots div.paper-padding-x > div.grid-x > div.cell > img
/assets/homepage_reviews_screenshot-e3f43d8a1b2de15981f59...
Matthew Gardner div.text-normal > div.hide-for-xlarge > div.cell > img.mb-1
/assets/reviewer_image1-63f003a2437fdab1c5ab51e13f673b4f4...
div.flex > a.full-width-section__link > div.full-width-section__image > img div.flex > a.full-width-section__link > div.full-width-section__image > img
/uploads/cms_content/image/69/homepage_Reach2025-LP-Featu...
div.flex > a.full-width-section__link > div.full-width-section__image > img div.flex > a.full-width-section__link > div.full-width-section__image > img
/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb...
div.flex > a.full-width-section__link > div.full-width-section__image > img div.flex > a.full-width-section__link > div.full-width-section__image > img
/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb...
div.flex > a.full-width-section__link > div.full-width-section__image > img div.flex > a.full-width-section__link > div.full-width-section__image > img
/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb...

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
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 2,663 KiB
User Timing marks and measures 10 user timings
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 2 animated elements found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 10 ms
Server Backend Latencies 560 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
Avoid large layout shifts 2 layout shifts found
INP breakdown
75

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

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Failing Elements
Research Boards nav.topnav__inner > div.flex > div.flex > a.elv-justify-center

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
Project Management div.grid-x > div.cell > div.selectable-menu__item-list > button#project-management
See all Project Management Software div.project-management > div#project-management-page > div.text-center > a.selectable-menu__link
Leave a Review div.cell > div.mx-2 > a > div.btn
find div.cell > div.mx-2 > div.full-width-section__title > span.fw-semibold
review div.cell > div.mx-2 > div.full-width-section__title > span.fw-semibold
Claim Your G2 Profile div.cell > div.mx-2 > a > div.btn

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Failing Elements
html.cors html.cors

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
div.flex > a.full-width-section__link > div.full-width-section__image > img div.flex > a.full-width-section__link > div.full-width-section__image > img
div.flex > a.full-width-section__link > div.full-width-section__image > img div.flex > a.full-width-section__link > div.full-width-section__image > img
div.flex > a.full-width-section__link > div.full-width-section__image > img div.flex > a.full-width-section__link > div.full-width-section__image > img
div.flex > a.full-width-section__link > div.full-width-section__image > img div.flex > a.full-width-section__link > div.full-width-section__image > img
div.flex > a.full-width-section__link > div.full-width-section__image > img div.flex > a.full-width-section__link > div.full-width-section__image > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Failing Elements
div.swiper-slide > div.grid > div.flex > a.full-width-section__link div.swiper-slide > div.grid > div.flex > a.full-width-section__link
div.swiper-slide > div.grid > div.flex > a.full-width-section__link div.swiper-slide > div.grid > div.flex > a.full-width-section__link
div.swiper-slide > div.grid > div.flex > a.full-width-section__link div.swiper-slide > div.grid > div.flex > a.full-width-section__link
div.swiper-slide > div.grid > div.flex > a.full-width-section__link div.swiper-slide > div.grid > div.flex > a.full-width-section__link
div.swiper-slide > div.grid > div.flex > a.full-width-section__link div.swiper-slide > div.grid > div.flex > a.full-width-section__link

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Failing Elements
Skip to Content div.position-relative > div.off-canvas-content > nav > a.btn
Skip to Navigation div.position-relative > div.off-canvas-content > nav > a.btn

These are opportunities to improve keyboard navigation in your application.

Best practices

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
Go to slide 1 div.paper-padding-x > div.swiper > div.carousel__pagination > span.swiper-pagination-bullet
Go to slide 2 div.paper-padding-x > div.swiper > div.carousel__pagination > span.swiper-pagination-bullet
Go to slide 3 div.paper-padding-x > div.swiper > div.carousel__pagination > span.swiper-pagination-bullet
Go to slide 4 div.paper-padding-x > div.swiper > div.carousel__pagination > span.swiper-pagination-bullet
Go to slide 5 div.paper-padding-x > div.swiper > div.carousel__pagination > span.swiper-pagination-bullet

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
EN div#subfooter-inner > div.language-selector > div.relative > button.elv-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]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`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
Elements use only permitted ARIA attributes
Document has a `<title>` element
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
ARIA IDs are unique
`[accesskey]` values are unique
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` 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
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has a valid value for its `[lang]` attribute
`<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
Links are distinguishable without relying on color.
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.
Identical links have the same purpose.
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

General

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

Deprecation / WarningSource
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge
AttributionReporting

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.g2.com/ line 155, col 13451
[GSI_LOGGER]: FedCM get() rejects with NetworkError: Error retrieving a token.
www.g2.com/ line 155, col 13451
Analytics not enabled
www.g2.com/ line 155, col 13451
Analytics not enabled
Not signed in with the identity provider.
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
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
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
85

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 may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Uncrawlable Link
Top Categories div.is-drilldown > ul.mobile-menu > li.mobile-menu__item > a.mobile-menu__content
li.mobile-menu__item > ul.menu > li.js-drilldown-back > a li.mobile-menu__item > ul.menu > li.js-drilldown-back > a
Cookie Preferences div.cell > ul.page-footer__section__body > li > a.js-log-click

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

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
div.flex > a.full-width-section__link > div.full-width-section__image > img div.flex > a.full-width-section__link > div.full-width-section__image > img
div.flex > a.full-width-section__link > div.full-width-section__image > img div.flex > a.full-width-section__link > div.full-width-section__image > img
div.flex > a.full-width-section__link > div.full-width-section__image > img div.flex > a.full-width-section__link > div.full-width-section__image > img
div.flex > a.full-width-section__link > div.full-width-section__image > img div.flex > a.full-width-section__link > div.full-width-section__image > img
div.flex > a.full-width-section__link > div.full-width-section__image > img div.flex > a.full-width-section__link > div.full-width-section__image > img

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

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
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Desktop audit not available for this result.

Send Feedback