Tools & Wizards About Us
locize.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

locize.com

localization & translation management platform | locize

Page Load Speed

2.2 sec in total

First Response

58 ms

Resources Loaded

1.3 sec

Page Rendered

844 ms

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 58 ms and then it took 2.1 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

locize.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

11/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value1,810 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.091

92/100

15%

TTI (Time to Interactive)

Value15.3 s

7/100

10%

Network Requests Diagram

locize.com

58 ms

locize.com

72 ms

bootstrap.min.css

56 ms

fontawesome.min.css

67 ms

brands.min.css

65 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 86% of them (72 requests) were addressed to the original Locize.com, 6% (5 requests) were made to Cdn.jsdelivr.net and 5% (4 requests) were made to Youtube-nocookie.com. The less responsive or slowest element that took the longest time to load (742 ms) belongs to the original domain Locize.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 472.7 kB (18%)

Content Size

2.6 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Locize.com 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 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 87.4 kB

  • Original 104.7 kB
  • After minification 95.1 kB
  • After compression 17.2 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 87.4 kB or 84% of the original size.

Image Optimization

-16%

Potential reduce by 383.2 kB

  • Original 2.4 MB
  • After minification 2.0 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 383.2 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 2.1 kB

  • Original 119.9 kB
  • After minification 119.9 kB
  • After compression 117.8 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 0 B

  • Original 59.8 kB
  • After minification 59.8 kB
  • After compression 59.8 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 has all CSS files already compressed.

Requests Breakdown

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

Requests Now

79

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 79 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

58 ms

locize.com

locize.com

72 ms

bootstrap.min.css

bootstrap.min.css

56 ms

fontawesome.min.css

fontawesome.min.css

67 ms

brands.min.css

brands.min.css

65 ms

solid.min.css

solid.min.css

64 ms

regular.min.css

regular.min.css

64 ms

simple-line-icons.css

simple-line-icons.css

52 ms

device-mockups.min.css

device-mockups.min.css

92 ms

main.min.css

main.min.css

96 ms

slick.css

slick.css

53 ms

locizify@6.0.9

locizify@6.0.9

62 ms

cookieconsent.min.css

cookieconsent.min.css

51 ms

email-decode.min.js

email-decode.min.js

68 ms

jquery.min.js

jquery.min.js

148 ms

bootstrap.min.js

bootstrap.min.js

93 ms

jquery.easing.min.js

jquery.easing.min.js

70 ms

main.min.js

main.min.js

167 ms

slick.min.js

slick.min.js

50 ms

cookieconsent.min.js

cookieconsent.min.js

56 ms

typed.umd.js

typed.umd.js

84 ms

e6c39eb5c72904eb7aa9a17d0c5f291f.svg

e6c39eb5c72904eb7aa9a17d0c5f291f.svg

374 ms

YQryHo1iHb8

YQryHo1iHb8

463 ms

locize_white.svg

locize_white.svg

375 ms

crozdesk.webp

crozdesk.webp

358 ms

portrait_black.png

portrait_black.png

374 ms

localization-management-platform.png

localization-management-platform.png

377 ms

zkb.png

zkb.png

355 ms

redcross.svg

redcross.svg

371 ms

abb.png

abb.png

390 ms

portrait_black.png

portrait_black.png

389 ms

integrate_s.jpg

integrate_s.jpg

390 ms

dashboard_s.jpg

dashboard_s.jpg

405 ms

incontext_editor_s.jpg

incontext_editor_s.jpg

403 ms

editor_s.jpg

editor_s.jpg

402 ms

translationmemory_s.jpg

translationmemory_s.jpg

416 ms

history_s.jpg

history_s.jpg

417 ms

review_s.jpg

review_s.jpg

421 ms

multitenant_s.jpg

multitenant_s.jpg

419 ms

i18next-frameworks.png

i18next-frameworks.png

419 ms

pay-for-what-you-use.png

pay-for-what-you-use.png

422 ms

portrait_white.png

portrait_white.png

435 ms

project_stat.jpg

project_stat.jpg

452 ms

flexible-integration.png

flexible-integration.png

440 ms

risk-free.png

risk-free.png

450 ms

project-progress.png

project-progress.png

467 ms

variable-pricing.png

variable-pricing.png

456 ms

localization_process.png

localization_process.png

506 ms

website.png

website.png

508 ms

mobile-app.png

mobile-app.png

508 ms

video-game.png

video-game.png

508 ms

platforms.png

platforms.png

508 ms

website-builder.png

website-builder.png

508 ms

any-software.png

any-software.png

740 ms

bg-cta-0.jpg

bg-cta-0.jpg

742 ms

locize_color.svg

locize_color.svg

553 ms

zinsli.png

zinsli.png

422 ms

2captcha.png

2captcha.png

422 ms

fa-solid-900.ttf

fa-solid-900.ttf

423 ms

fa-regular-400.ttf

fa-regular-400.ttf

439 ms

fa-brands-400.ttf

fa-brands-400.ttf

428 ms

airtime.png

airtime.png

422 ms

airtm.png

airtm.png

422 ms

alchemist.png

alchemist.png

419 ms

wusoma.png

wusoma.png

412 ms

appointedd.png

appointedd.png

410 ms

barntools.png

barntools.png

407 ms

wonderbox.png

wonderbox.png

398 ms

bethesda.png

bethesda.png

397 ms

span.png

span.png

396 ms

tegoly.png

tegoly.png

396 ms

spt.png

spt.png

386 ms

worldshopping.png

worldshopping.png

384 ms

vgpro.png

vgpro.png

380 ms

willskill.png

willskill.png

382 ms

schoolparrot.png

schoolparrot.png

382 ms

withlocals.png

withlocals.png

374 ms

watchduty.png

watchduty.png

368 ms

wavy.png

wavy.png

355 ms

czapp.jpg

czapp.jpg

354 ms

www-player.css

www-player.css

15 ms

www-embed-player.js

www-embed-player.js

55 ms

base.js

base.js

103 ms

syarah.png

syarah.png

351 ms

Accessibility Review

locize.com accessibility score

78

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best Practices

locize.com best practices score

83

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

High

Page has valid source maps

SEO Factors

locize.com SEO score

90

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: