Tools & Wizards About Us
lokalise.co screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

lokalise.co

A Localization and Translation Software Tool | Lokalise

Page Load Speed

2.8 sec in total

First Response

31 ms

Resources Loaded

2 sec

Page Rendered

738 ms

lokalise.co screenshot

About Website

Click here to check amazing Lokalise content for United States. Otherwise, check out these important facts you probably never knew about lokalise.co

Lokalise is a continuous localization and translation management platform. It integrates into your development workflow so you can ship localized products, faster.

Visit lokalise.co

Key Findings

We analyzed Lokalise.co page load time and found that the first response time was 31 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

lokalise.co performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value5,230 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.06

98/100

15%

TTI (Time to Interactive)

Value23.6 s

1/100

10%

Network Requests Diagram

lokalise.co

31 ms

lokalise.com

660 ms

OtAutoBlock.js

39 ms

otSDKStub.js

49 ms

0babe6bf-4f40-4347-8862-4286fa0e75d1.json

22 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Lokalise.co, 91% (48 requests) were made to Lokalise.com and 6% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Lokalise.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 473.3 kB (36%)

Content Size

1.3 MB

After Optimization

824.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Lokalise.co main page is 1.3 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. 35% of websites need less resources to load. Images take 547.4 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 420.5 kB

  • Original 491.4 kB
  • After minification 461.9 kB
  • After compression 70.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 420.5 kB or 86% of the original size.

Image Optimization

-3%

Potential reduce by 14.6 kB

  • Original 547.4 kB
  • After minification 532.8 kB

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. Lokalise images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 38.1 kB

  • Original 259.1 kB
  • After minification 259.1 kB
  • After compression 221.0 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 38.1 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (10%)

Requests Now

48

After Optimization

43

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

lokalise.co

lokalise.co

31 ms

lokalise.com

lokalise.com

660 ms

OtAutoBlock.js

OtAutoBlock.js

39 ms

otSDKStub.js

otSDKStub.js

49 ms

0babe6bf-4f40-4347-8862-4286fa0e75d1.json

0babe6bf-4f40-4347-8862-4286fa0e75d1.json

22 ms

location

location

121 ms

logo.1e63f0dd.svg

logo.1e63f0dd.svg

92 ms

arrow_01_hover.e75ad66e.svg

arrow_01_hover.e75ad66e.svg

194 ms

arrow_01.075778a9.svg

arrow_01.075778a9.svg

285 ms

arrow-april-2024.d6514b38.svg

arrow-april-2024.d6514b38.svg

289 ms

4225-Group.svg

4225-Group.svg

286 ms

4273-Group.svg

4273-Group.svg

290 ms

4272-1650-811-Capterra_logo_bw_new%201.svg

4272-1650-811-Capterra_logo_bw_new%201.svg

288 ms

4062-Company%20Name%3Dappier.svg

4062-Company%20Name%3Dappier.svg

291 ms

4254-Logo.svg

4254-Logo.svg

375 ms

4234-Logo%20%281%29.svg

4234-Logo%20%281%29.svg

377 ms

4074-Company%20Name%3DLife360.svg

4074-Company%20Name%3DLife360.svg

651 ms

4068-Company%20Name%3Dpleo.svg

4068-Company%20Name%3Dpleo.svg

469 ms

4063-Company%20Name%3DKry.svg

4063-Company%20Name%3DKry.svg

384 ms

4233-Logo%20%282%29.svg

4233-Logo%20%282%29.svg

382 ms

4235-Logo%20%283%29.svg

4235-Logo%20%283%29.svg

466 ms

4250-Logo%20%284%29.svg

4250-Logo%20%284%29.svg

471 ms

4251-Logo%20%285%29.svg

4251-Logo%20%285%29.svg

473 ms

4072-Company%20Name%3DElli.svg

4072-Company%20Name%3DElli.svg

566 ms

4253-Logo%20%286%29.svg

4253-Logo%20%286%29.svg

557 ms

4052-Company%20Name%3Dwithings.svg

4052-Company%20Name%3Dwithings.svg

559 ms

4256-Vector%20%281%29.svg

4256-Vector%20%281%29.svg

560 ms

4196-3%20hours%201.svg

4196-3%20hours%201.svg

564 ms

4138-Group%20627998.svg

4138-Group%20627998.svg

661 ms

FactorA-Regular.woff

FactorA-Regular.woff

831 ms

FactorA-Medium.woff

FactorA-Medium.woff

744 ms

FactorA-Bold.woff

FactorA-Bold.woff

750 ms

runtime.0c796a0d.js

runtime.0c796a0d.js

626 ms

0.3612fbd5.js

0.3612fbd5.js

800 ms

app.7b70157d.js

app.7b70157d.js

892 ms

4114-integration_gitHub.svg

4114-integration_gitHub.svg

713 ms

4115-Group%20627405.svg

4115-Group%20627405.svg

818 ms

4113-Group%20628030.svg

4113-Group%20628030.svg

849 ms

4109-Group%20628035.svg

4109-Group%20628035.svg

850 ms

4111-integration_bitbucket.svg

4111-integration_bitbucket.svg

886 ms

4112-Where%20content%20drives%20business%20momentum%20_%20Contentful-50%201.svg

4112-Where%20content%20drives%20business%20momentum%20_%20Contentful-50%201.svg

888 ms

4106-integration_azure_repos.svg

4106-integration_azure_repos.svg

918 ms

4108-Symbol.svg

4108-Symbol.svg

872 ms

4107-Adobe_XD_CC_icon%202.svg

4107-Adobe_XD_CC_icon%202.svg

772 ms

4110-Group%20628038.svg

4110-Group%20628038.svg

734 ms

collapse-arrow.d831407d.svg

collapse-arrow.d831407d.svg

732 ms

4203-Connect%402x.png

4203-Connect%402x.png

825 ms

4198-Automate%402x.png

4198-Automate%402x.png

824 ms

4264-Translate%402x.png

4264-Translate%402x.png

735 ms

4271-Review%402x.png

4271-Review%402x.png

1101 ms

4197-Analyze%402x.png

4197-Analyze%402x.png

824 ms

4224-icons8-money%201.svg

4224-icons8-money%201.svg

732 ms

footer_logo.81a91bfb.svg

footer_logo.81a91bfb.svg

734 ms

Accessibility Review

lokalise.co accessibility score

80

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

lokalise.co best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

lokalise.co SEO score

86

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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 Lokalise.co 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 Lokalise.co 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

lokalise.co

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