Tools & Wizards About Us
locize.com screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    57% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 85

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 88

    SEO

    Google-friendlier than
    66% of websites

locize.com

localization & translation management platform | locize

Page Load Speed

4.6 sec in total

First Response

62 ms

Resources Loaded

2.4 sec

Page Rendered

2.1 sec

locize.com screenshot

About Website

Visit locize.com now to see the best up-to-date Locize content for United States and also check out these interesting facts you probably never knew about locize.com

As a localization and translation management platform, locize enables you to separate your development and translation process.

Visit locize.com

Key Findings

We analyzed Locize.com page load time and found that the first response time was 62 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

locize.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value1,300 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.091

92/100

15%

TTI (Time to Interactive)

Value11.9 s

17/100

10%

Network Requests Diagram

locize.com

62 ms

bootstrap.min.css

49 ms

css

74 ms

css

86 ms

css

102 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 67% of them (64 requests) were addressed to the original Locize.com, 17% (16 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Youtube-nocookie.com. The less responsive or slowest element that took the longest time to load (863 ms) belongs to the original domain Locize.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 600.1 kB (25%)

Content Size

2.4 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Locize.com main page is 2.4 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. 85% 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. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 70.9 kB

  • Original 85.5 kB
  • After minification 77.2 kB
  • After compression 14.6 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 70.9 kB or 83% of the original size.

Image Optimization

-11%

Potential reduce by 211.0 kB

  • Original 1.9 MB
  • After minification 1.7 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. Obviously, Locize needs image optimization as it can save up to 211.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-57%

Potential reduce by 6.8 kB

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

CSS Optimization

-85%

Potential reduce by 311.4 kB

  • Original 368.5 kB
  • After minification 368.3 kB
  • After compression 57.0 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. Locize.com needs all CSS files to be minified and compressed as it can save up to 311.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (27%)

Requests Now

75

After Optimization

55

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

locize.com

locize.com

62 ms

bootstrap.min.css

bootstrap.min.css

49 ms

css

css

74 ms

css

css

86 ms

css

css

102 ms

font-awesome.min.css

font-awesome.min.css

62 ms

simple-line-icons.css

simple-line-icons.css

69 ms

device-mockups.min.css

device-mockups.min.css

79 ms

main.min.css

main.min.css

64 ms

slick.css

slick.css

81 ms

locizify@5

locizify@5

495 ms

cookieconsent.min.css

cookieconsent.min.css

86 ms

email-decode.min.js

email-decode.min.js

61 ms

jquery.min.js

jquery.min.js

74 ms

bootstrap.min.js

bootstrap.min.js

92 ms

jquery.easing.min.js

jquery.easing.min.js

85 ms

main.min.js

main.min.js

82 ms

slick.min.js

slick.min.js

87 ms

cookieconsent.min.js

cookieconsent.min.js

86 ms

locizify@5.2.9

locizify@5.2.9

85 ms

locizify.min.js

locizify.min.js

386 ms

regensburg.jpg

regensburg.jpg

210 ms

YQryHo1iHb8

YQryHo1iHb8

473 ms

bg-pattern2.png

bg-pattern2.png

188 ms

locize_white.svg

locize_white.svg

185 ms

portrait_black.png

portrait_black.png

190 ms

localization-management-platform.jpg

localization-management-platform.jpg

188 ms

portrait_black.png

portrait_black.png

192 ms

integrate_s.jpg

integrate_s.jpg

183 ms

dashboard_s.jpg

dashboard_s.jpg

447 ms

incontext_editor_s.jpg

incontext_editor_s.jpg

442 ms

editor_s.jpg

editor_s.jpg

439 ms

translationmemory_s.jpg

translationmemory_s.jpg

448 ms

history_s.jpg

history_s.jpg

447 ms

review_s.jpg

review_s.jpg

445 ms

multitenant_s.jpg

multitenant_s.jpg

478 ms

i18next-frameworks.png

i18next-frameworks.png

489 ms

localization-pricing.webp

localization-pricing.webp

488 ms

bookingfactory.png

bookingfactory.png

488 ms

hypertrend.png

hypertrend.png

486 ms

abb.png

abb.png

489 ms

portrait_white.png

portrait_white.png

584 ms

project_stat.jpg

project_stat.jpg

580 ms

localization_process.png

localization_process.png

582 ms

website_localization.png

website_localization.png

579 ms

app_localization.png

app_localization.png

577 ms

game_localization.png

game_localization.png

578 ms

platform_localization.png

platform_localization.png

682 ms

website_builder.png

website_builder.png

674 ms

whatever_software_localization.png

whatever_software_localization.png

674 ms

bg-cta-0.jpg

bg-cta-0.jpg

671 ms

locize_color.svg

locize_color.svg

676 ms

ieVl2ZhZI2eCN5jzbjEETS9weq8-19K7CA.ttf

ieVl2ZhZI2eCN5jzbjEETS9weq8-19K7CA.ttf

408 ms

ieVi2ZhZI2eCN5jzbjEETS9weq8-33mZGCQYag.ttf

ieVi2ZhZI2eCN5jzbjEETS9weq8-33mZGCQYag.ttf

353 ms

ieVi2ZhZI2eCN5jzbjEETS9weq8-32meGCQYag.ttf

ieVi2ZhZI2eCN5jzbjEETS9weq8-32meGCQYag.ttf

406 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPPjd5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPPjd5a7dvg.ttf

403 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPHjc5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPHjc5a7dvg.ttf

402 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPCbd5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPCbd5a7dvg.ttf

401 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPHjd5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPHjd5a7dvg.ttf

415 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPErd5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPErd5a7dvg.ttf

415 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPKba5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPKba5a7dvg.ttf

414 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPJ_a5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPJ_a5a7dvg.ttf

417 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPPja5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPPja5a7dvg.ttf

417 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPNHa5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPNHa5a7dvg.ttf

417 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

496 ms

ieVg2ZhZI2eCN5jzbjEETS9weq8-19eDpCEobdNc.ttf

ieVg2ZhZI2eCN5jzbjEETS9weq8-19eDpCEobdNc.ttf

499 ms

ieVj2ZhZI2eCN5jzbjEETS9weq8-19eLDwM4.ttf

ieVj2ZhZI2eCN5jzbjEETS9weq8-19eLDwM4.ttf

497 ms

ieVg2ZhZI2eCN5jzbjEETS9weq8-19eDtCYobdNc.ttf

ieVg2ZhZI2eCN5jzbjEETS9weq8-19eDtCYobdNc.ttf

452 ms

Simple-Line-Icons.ttf

Simple-Line-Icons.ttf

860 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

863 ms

wuxus.png

wuxus.png

594 ms

withlocals.png

withlocals.png

596 ms

wusoma.png

wusoma.png

349 ms

2captcha.png

2captcha.png

351 ms

alchemist.png

alchemist.png

597 ms

appointedd.png

appointedd.png

593 ms

atroo.png

atroo.png

597 ms

beelance.png

beelance.png

600 ms

airtm.png

airtm.png

602 ms

worldshopping.png

worldshopping.png

598 ms

shoprepublic.png

shoprepublic.png

602 ms

spiff3d.svg

spiff3d.svg

602 ms

vgpro.png

vgpro.png

654 ms

retraced.png

retraced.png

658 ms

syarah.png

syarah.png

655 ms

tegoly.svg

tegoly.svg

658 ms

www-player.css

www-player.css

144 ms

www-embed-player.js

www-embed-player.js

179 ms

base.js

base.js

342 ms

fetch-polyfill.js

fetch-polyfill.js

135 ms

span.png

span.png

650 ms

skodel.png

skodel.png

621 ms

spt.png

spt.png

636 ms

wavy.png

wavy.png

636 ms

redcross.svg

redcross.svg

637 ms

quotepro.png

quotepro.png

635 ms

Accessibility Review

locize.com 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

locize.com best practices score

85

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

locize.com SEO score

88

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

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

High

Tap targets are not sized appropriately

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 Locize.com 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 Locize.com 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

locize.com

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