Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

crowdin.net

Localization Management Platform for agile teams | Crowdin

Page Load Speed

2.4 sec in total

First Response

14 ms

Resources Loaded

753 ms

Page Rendered

1.6 sec

crowdin.net screenshot

About Website

Click here to check amazing Crowdin content for Russia. Otherwise, check out these important facts you probably never knew about crowdin.net

Crowdin's localization management platform is a technology solution for your team. Translate and update content for your multilingual product with our cloud software.

Visit crowdin.net

Key Findings

We analyzed Crowdin.net page load time and found that the first response time was 14 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

crowdin.net performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value7.6 s

25/100

10%

TBT (Total Blocking Time)

Value1,610 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.13

81/100

15%

TTI (Time to Interactive)

Value15.3 s

7/100

10%

Network Requests Diagram

crowdin.net

14 ms

crowdin.com

76 ms

css2

42 ms

css2

69 ms

canvas@2.7.0

51 ms

Our browser made a total of 160 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Crowdin.net, 89% (142 requests) were made to D2gma3rgtloi6d.cloudfront.net and 6% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (226 ms) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 424.8 kB (16%)

Content Size

2.6 MB

After Optimization

2.2 MB

In fact, the total size of Crowdin.net main page is 2.6 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 258.4 kB

  • Original 338.3 kB
  • After minification 273.8 kB
  • After compression 79.9 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 64.5 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 258.4 kB or 76% of the original size.

Image Optimization

-10%

Potential reduce by 165.9 kB

  • Original 1.7 MB
  • After minification 1.5 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Crowdin images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 332 B

  • Original 492.4 kB
  • After minification 492.4 kB
  • After compression 492.1 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 60 B

  • Original 91.5 kB
  • After minification 91.5 kB
  • After compression 91.5 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Crowdin.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 53 (36%)

Requests Now

146

After Optimization

93

The browser has sent 146 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Crowdin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

crowdin.net accessibility score

87

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

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.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

crowdin.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

crowdin.net SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Crowdin.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Crowdin.net main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph data is detected on the main page of Crowdin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: