6.6 sec in total
230 ms
3.3 sec
3.1 sec
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.coWe analyzed Lokalise.co page load time and found that the first response time was 230 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
lokalise.co performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value7.0 s
6/100
25%
Value42.4 s
0/100
10%
Value49,210 ms
0/100
30%
Value0.063
97/100
15%
Value65.6 s
0/100
10%
230 ms
388 ms
592 ms
109 ms
78 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Lokalise.co, 46% (23 requests) were made to Lokalise.com and 16% (8 requests) were made to Fast.wistia.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Lokalise.com.
Page size can be reduced by 294.3 kB (49%)
600.7 kB
306.4 kB
In fact, the total size of Lokalise.co main page is 600.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 354.5 kB which makes up the majority of the site volume.
Potential reduce by 294.1 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 294.1 kB or 83% of the original size.
Potential reduce by 214 B
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.
Number of requests can be reduced by 28 (68%)
41
13
The browser has sent 41 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 24 to 1 for JavaScripts and as a result speed up the page load time.
lokalise.co
230 ms
lokalise.co
388 ms
lokalise.com
592 ms
optimize.js
109 ms
a6ce0407b0b2e1f3d9bd9111c1b16281.js
78 ms
tz1efucl7n.jsonp
499 ms
E-v1.js
521 ms
runtime.0c796a0d.js
494 ms
0.c92a3640.js
1012 ms
app.e4d6a7ff.js
1010 ms
revenue.js
848 ms
logo.6c425399.svg
640 ms
arrow_01_hover.e75ad66e.svg
642 ms
arrow_01.075778a9.svg
638 ms
google-btn.606d502b.svg
741 ms
1272-Mastercard_logo.svg
742 ms
1273-Starbucks_logo.svg
739 ms
1277-Withings_logo.svg
743 ms
1600-Hyandai_logo.svg
848 ms
2201-Lokalise_Arduino_logo.svg
851 ms
614-Revolut.svg
849 ms
footer_logo.81a91bfb.svg
846 ms
ct
477 ms
GraphikLCTT-Regular.woff
789 ms
Graphik-Medium-Web.woff
638 ms
GraphikLCTT-Semibold.woff
973 ms
popover.js
14 ms
wistia-mux.js
37 ms
flashPlayer.js
42 ms
captions.js
30 ms
share-v2.js
32 ms
postRoll-v2.js
53 ms
fbevents.js
149 ms
bat.js
284 ms
js
275 ms
js
279 ms
cheq-ppc-invalid-users
560 ms
tc_imp.gif
118 ms
220830059176287
111 ms
linkedin.js
139 ms
logo_mobile.563320c1.svg
140 ms
arrow_right_02.13fa92ba.svg
137 ms
42a6841a6b801a44ac0137b69cf3cebe.jpg
106 ms
conversion_async.js
57 ms
42a6841a6b801a44ac0137b69cf3cebe.jpg
97 ms
101 ms
45 ms
54 ms
41 ms
30 ms
lokalise.co accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
lokalise.co best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
lokalise.co SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
EN
EN
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.
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: