Mobile 375 × 812

Desktop 1440 × 900

Score: 74 / 100
Based on 8 categories, 0 sections
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
HSTS header is missing
No Content-Security-Policy header found
1 link(s) with no accessible text
12 button(s) with no accessible text
[](https://beavercheck.com/results/fc3894cc-31d9-bfb3-0c9e-a7a18b389a08)<a href="https://beavercheck.com/results/fc3894cc-31d9-bfb3-0c9e-a7a18b389a08"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.crowdin.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.crowdin.comThis badge auto-updates with your latest scan result.
Thanks for your feedback!
Industry-standard audits powered by Google Lighthouse.
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.
5.11 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
5.43 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.95 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.308
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
5.11 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.
20.23 s
Audit breakdown by category with detailed findings.
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.
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
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.
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.
| URL | Transfer Size | Duration |
|---|---|---|
| /css2?family=Manrope:wght@200..800&family=Noto+Sans:ital,... | 1.4 KiB | 867 ms |
| d2gma3rgtloi6d.cloudfront.net/astro-website/_astro/_slug_.BJm3mwtx.css | 34.0 KiB | 512 ms |
| d2gma3rgtloi6d.cloudfront.net/astro-website/_astro/_slug_.DAQTXMSo.css | 3.0 KiB | 826 ms |
| static.hsappstatic.net/MeetingsEmbed/ex/MeetingsEmbedCode.js | 2.6 KiB | 818 ms |
| cdn-cookieyes.com/client_data/2dabfbbec8b71e267115f6a5/script.js | 9.4 KiB | 976 ms |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| hog.crowdin.com/static/array.js | 60.0 s | 51.3 KiB |
| static.hsappstatic.net/MeetingsEmbed/ex/MeetingsEmbedCode.js | 60.0 s | 2.6 KiB |
| cdn-cookieyes.com/assets/images/close.svg | 36000.0 s | 868 B |
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
| URL | Resource Size | Est Savings | |
|---|---|---|---|
Crowdin Editor div.bg-purple-200 > div.max-w-[80%] > div.absolute > img.w-full | d2gma3rgtloi6d.cloudfront.net/astro-website/_astro/editor.CM5mIc2y_ZkstQN.webp | 63.0 KiB | 59.3 KiB |
Crowdin Reports Page div.bg-purple-200 > div.max-w-[80%] > div.absolute > img.w-full | d2gma3rgtloi6d.cloudfront.net/astro-website/_astro/reports.DOkbjs3X_ZhtB4i.webp | 54.2 KiB | 52.4 KiB |
Crowdin Project Page div.bg-purple-200 > div.max-w-[80%] > div.relative > img.w-full | d2gma3rgtloi6d.cloudfront.net/astro-website/_astro/project.Cgg7bTKw_ZGkzUC.webp | 46.9 KiB | 42.3 KiB |
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.
| URL | Time Spent |
|---|---|
| www.crowdin.com/ | 1.0 s |
| crowdin.com/ | 0.0 ms |
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
| Element | Layout shift score |
|---|---|
Based on 669 reviews on G2 section.py-10 > div.container > div.grid > div.flex | 0.301 |
div.container > div.grid > div.flex > div.flex div.container > div.grid > div.flex > div.flex | 0.007 |
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.
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.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
| URL | Transfer Size | Est Savings |
|---|---|---|
| b1cb57fb136a.3535c7cd.us-east-1.token.awswaf.com/b1cb57fb136a/challenge.js | 573.5 KiB | 297.2 KiB |
| b1cb57fb136a.us-east-1.captcha-sdk.awswaf.com/b1cb57fb136a/jsapi.js | 83.8 KiB | 72.1 KiB |
| gtm-sst.crowdin.com/gtm.js?id=GTM-MW5LV72 | 155.8 KiB | 65.0 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-W87XVT8 | 122.9 KiB | 62.0 KiB |
| /gtag/js?id=G-SRNRQ29Q3E&cx=c>m=4e6460&sign=7210a9191e8... | 173.1 KiB | 59.3 KiB |
| d2gma3rgtloi6d.cloudfront.net/astro-website/_astro/proxy.BPgS-yi0.js | 37.7 KiB | 28.5 KiB |
| hog.crowdin.com/static/array.js | 51.0 KiB | 26.5 KiB |
| d2gma3rgtloi6d.cloudfront.net/astro-website/_astro/client.BgplVUld.js | 56.2 KiB | 22.9 KiB |
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.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| crowdin.com/ | 3.0 s | 62 ms | 8.1 ms |
| d2gma3rgtloi6d.cloudfront.net/astro-website/_astro/client.BgplVUld.js | 1.3 s | 767 ms | 7.1 ms |
| Unattributable | 1.2 s | 128 ms | 0.0 ms |
| b1cb57fb136a.3535c7cd.us-east-1.token.awswaf.com/b1cb57fb136a/challenge.js | 1.2 s | 1.0 s | 115 ms |
| cdn-cookieyes.com/client_data/2dabfbbec8b71e267115f6a5/banner.js | 555 ms | 388 ms | 2.3 ms |
| gtm-sst.crowdin.com/gtm.js?id=GTM-MW5LV72 | 407 ms | 317 ms | 51 ms |
| /gtag/js?id=G-SRNRQ29Q3E&cx=c>m=4e6460&sign=7210a9191e8... | 377 ms | 300 ms | 72 ms |
| www.googletagmanager.com/gtm.js?id=GTM-W87XVT8 | 312 ms | 195 ms | 46 ms |
| cdn-cookieyes.com/client_data/2dabfbbec8b71e267115f6a5/script.js | 255 ms | 239 ms | 2.4 ms |
| hog.crowdin.com/static/array.js | 244 ms | 213 ms | 17 ms |
| d2gma3rgtloi6d.cloudfront.net/astro-website/_astro/proxy.BPgS-yi0.js | 60 ms | 14 ms | 0.5 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
| Category | Time Spent |
|---|---|
| Script Evaluation | 3.7 s |
| Other | 2.7 s |
| Style & Layout | 1.4 s |
| Rendering | 732 ms |
| Script Parsing & Compilation | 382 ms |
| Parse HTML & CSS | 233 ms |
| Garbage Collection | 144 ms |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
| URL | |
|---|---|
Editor div.bg-teal-200 > div.bg-white > div.bg-gradient-to-br > img.w-full | /astro-website/_astro/editor-sidebyside.DawZXTed.webp |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
| Failing Elements |
|---|
GitHub div.bg-white > div.flex > div.flex > div.w-8 |
GitLab div.bg-white > div.flex > div.flex > div.w-8 |
Bitbucket div.bg-white > div.flex > div.flex > div.w-8 |
Figma div.bg-white > div.flex > div.flex > div.w-8 |
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.
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
| Failing Elements |
|---|
div.bg-gradient-to-br > div.bg-background > div.flex > button.p-1.5 div.bg-gradient-to-br > div.bg-background > div.flex > button.p-1.5 |
div.col-span-12 > astro-island > div.flex > button div.col-span-12 > astro-island > div.flex > button |
div.col-span-12 > astro-island > div.flex > button div.col-span-12 > astro-island > div.flex > button |
div.col-span-12 > astro-island > div.flex > button div.col-span-12 > astro-island > div.flex > button |
div.flex > astro-island > div.flex > button div.flex > astro-island > div.flex > button |
div.flex > astro-island > div.flex > button div.flex > astro-island > div.flex > button |
div.flex > astro-island > div.flex > button div.flex > astro-island > div.flex > button |
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.container > div.grid > div.flex > a div.container > div.grid > div.flex > a |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
| Failing Elements |
|---|
* Crowdin.com UI section#screenshots > div.container > div.bg-purple-200 > p.text-xs |
With Crowdin div.container > div.grid > div.bg-primary > div.inline-block |
Small Business div.bg-purple-200 > div.transition-opacity > div.text-center > p.text-muted-foreground |
These are opportunities to improve the legibility of your content.
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 3 div.relative > div.flex > div.flex > button.h-2 |
Go to slide 4 div.relative > div.flex > div.flex > button.h-2 |
Go to slide 5 div.relative > div.flex > div.flex > button.h-2 |
Go to slide 6 div.relative > div.flex > div.flex > button.h-2 |
These items highlight common accessibility best practices.
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
| Source | Description |
|---|---|
The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy. |
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
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.
Industry-standard audits powered by Google Lighthouse. — Desktop
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.
1.97 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
4.64 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
192 ms
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.97 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.
4.66 s
Audit breakdown by category with detailed findings.
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.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
| URL | Resource Size | Est Savings | |
|---|---|---|---|
Crowdin Editor div.bg-purple-200 > div.max-w-[80%] > div.absolute > img.w-full | d2gma3rgtloi6d.cloudfront.net/astro-website/_astro/editor.CM5mIc2y_ZkstQN.webp | 63.0 KiB | 51.2 KiB |
Crowdin Reports Page div.bg-purple-200 > div.max-w-[80%] > div.absolute > img.w-full | d2gma3rgtloi6d.cloudfront.net/astro-website/_astro/reports.DOkbjs3X_ZhtB4i.webp | 54.2 KiB | 48.4 KiB |
Crowdin Project Page div.bg-purple-200 > div.max-w-[80%] > div.relative > img.w-full | d2gma3rgtloi6d.cloudfront.net/astro-website/_astro/project.Cgg7bTKw_ZGkzUC.webp | 46.9 KiB | 32.8 KiB |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
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.
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.
| URL | Transfer Size | Duration |
|---|---|---|
| /css2?family=Manrope:wght@200..800&family=Noto+Sans:ital,... | 1.4 KiB | 291 ms |
| d2gma3rgtloi6d.cloudfront.net/astro-website/_astro/_slug_.BJm3mwtx.css | 34.0 KiB | 120 ms |
| static.hsappstatic.net/MeetingsEmbed/ex/MeetingsEmbedCode.js | 2.6 KiB | 265 ms |
| d2gma3rgtloi6d.cloudfront.net/astro-website/_astro/_slug_.DAQTXMSo.css | 3.0 KiB | 276 ms |
| cdn-cookieyes.com/client_data/2dabfbbec8b71e267115f6a5/script.js | 9.4 KiB | 258 ms |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| hog.crowdin.com/static/array.js | 60.0 s | 51.3 KiB |
| static.hsappstatic.net/MeetingsEmbed/ex/MeetingsEmbedCode.js | 60.0 s | 2.6 KiB |
| cdn-cookieyes.com/assets/images/close.svg | 36000.0 s | 868 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.
| URL | Time Spent |
|---|---|
| www.crowdin.com/ | 486 ms |
| crowdin.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.
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.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
| URL | Transfer Size | Est Savings |
|---|---|---|
| b1cb57fb136a.3535c7cd.us-east-1.token.awswaf.com/b1cb57fb136a/challenge.js | 573.4 KiB | 297.2 KiB |
| b1cb57fb136a.us-east-1.captcha-sdk.awswaf.com/b1cb57fb136a/jsapi.js | 83.6 KiB | 71.9 KiB |
| gtm-sst.crowdin.com/gtm.js?id=GTM-MW5LV72 | 155.8 KiB | 64.9 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-W87XVT8 | 122.9 KiB | 62.0 KiB |
| /gtag/js?id=G-SRNRQ29Q3E&cx=c>m=4e6460&sign=8fd1e5b3e4a... | 173.1 KiB | 59.5 KiB |
| d2gma3rgtloi6d.cloudfront.net/astro-website/_astro/proxy.BPgS-yi0.js | 37.7 KiB | 28.1 KiB |
| hog.crowdin.com/static/array.js | 51.0 KiB | 26.5 KiB |
| d2gma3rgtloi6d.cloudfront.net/astro-website/_astro/client.BgplVUld.js | 56.2 KiB | 22.7 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
| URL | |
|---|---|
Editor div.bg-teal-200 > div.bg-white > div.bg-gradient-to-br > img.w-full | /astro-website/_astro/editor-sidebyside.DawZXTed.webp |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
| Failing Elements |
|---|
GitHub div.bg-white > div.flex > div.flex > div.w-8 |
GitLab div.bg-white > div.flex > div.flex > div.w-8 |
Bitbucket div.bg-white > div.flex > div.flex > div.w-8 |
Figma div.bg-white > div.flex > div.flex > div.w-8 |
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.
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
| Failing Elements |
|---|
div.bg-gradient-to-br > div.bg-background > div.flex > button.p-1.5 div.bg-gradient-to-br > div.bg-background > div.flex > button.p-1.5 |
div.col-span-12 > astro-island > div.flex > button div.col-span-12 > astro-island > div.flex > button |
div.col-span-12 > astro-island > div.flex > button div.col-span-12 > astro-island > div.flex > button |
div.col-span-12 > astro-island > div.flex > button div.col-span-12 > astro-island > div.flex > button |
div.flex > astro-island > div.flex > button div.flex > astro-island > div.flex > button |
div.flex > astro-island > div.flex > button div.flex > astro-island > div.flex > button |
div.flex > astro-island > div.flex > button div.flex > astro-island > div.flex > button |
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.container > div.grid > div.flex > a div.container > div.grid > div.flex > a |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
| Failing Elements |
|---|
* Crowdin.com UI section#screenshots > div.container > div.bg-purple-200 > p.text-xs |
With Crowdin div.container > div.grid > div.bg-primary > div.inline-block |
Small Business div.bg-purple-200 > div.transition-opacity > div.text-center > p.text-muted-foreground |
These are opportunities to improve the legibility of your content.
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 3 div.relative > div.flex > div.flex > button.h-2 |
Go to slide 4 div.relative > div.flex > div.flex > button.h-2 |
Go to slide 5 div.relative > div.flex > div.flex > button.h-2 |
Go to slide 6 div.relative > div.flex > div.flex > button.h-2 |
These items highlight common accessibility best practices.
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
| Source | Description |
|---|---|
The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy. |
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
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.
Send Feedback