Tools & Wizards About Us
proz.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

proz.com

Freelance translators & Translation companies | ProZ.com

Page Load Speed

47 sec in total

First Response

355 ms

Resources Loaded

39 sec

Page Rendered

7.7 sec

proz.com screenshot

About Website

Click here to check amazing ProZ content for United States. Otherwise, check out these important facts you probably never knew about proz.com

Translation service and translation jobs for freelance translators and translation agencies.

Visit proz.com

Key Findings

We analyzed Proz.com page load time and found that the first response time was 355 ms and then it took 46.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

proz.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

40/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value1,830 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.156

74/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

proz.com

355 ms

www.proz.com

1425 ms

bootstrap_minimal.css

897 ms

font-awesome.min.css

2240 ms

bootstrap.min.css

2822 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 14% of them (13 requests) were addressed to the original Proz.com, 18% (17 requests) were made to Cdn4.proz.com and 9% (8 requests) were made to Cdn3.proz.com. The less responsive or slowest element that took the longest time to load (8 sec) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (61%)

Content Size

2.2 MB

After Optimization

846.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Proz.com main page is 2.2 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. 80% 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. Javascripts take 999.8 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 105.3 kB

  • Original 128.7 kB
  • After minification 114.9 kB
  • After compression 23.4 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 13.8 kB, which is 11% 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 105.3 kB or 82% of the original size.

Image Optimization

-6%

Potential reduce by 24.6 kB

  • Original 399.6 kB
  • After minification 375.0 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. ProZ images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 642.2 kB

  • Original 999.8 kB
  • After minification 999.7 kB
  • After compression 357.6 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 642.2 kB or 64% of the original size.

CSS Optimization

-86%

Potential reduce by 541.0 kB

  • Original 631.2 kB
  • After minification 539.5 kB
  • After compression 90.3 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. Proz.com needs all CSS files to be minified and compressed as it can save up to 541.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 65 (77%)

Requests Now

84

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

proz.com

proz.com

355 ms

www.proz.com

www.proz.com

1425 ms

bootstrap_minimal.css

bootstrap_minimal.css

897 ms

font-awesome.min.css

font-awesome.min.css

2240 ms

bootstrap.min.css

bootstrap.min.css

2822 ms

bootstrap_custom_proz.css

bootstrap_custom_proz.css

836 ms

nav_and_footer_2017.css

nav_and_footer_2017.css

1247 ms

in.js

in.js

1738 ms

platform.js

platform.js

3309 ms

b=css&f=global.css,fslev1.css&1501207060

b=css&f=global.css,fslev1.css&1501207060

1796 ms

index.css&1496193544

index.css&1496193544

1796 ms

ptc-impromptu.css&1468261672

ptc-impromptu.css&1468261672

1691 ms

jquery-ui.min.css&1468261673

jquery-ui.min.css&1468261673

1690 ms

jquery.autocomplete.css&1468261672

jquery.autocomplete.css&1468261672

2158 ms

thickbox.css&1468261672

thickbox.css&1468261672

1690 ms

b=js&f=jquery-1.10.2.min.js,jquery-migrate-1.2.1.min.js,tooltip_v5.js,main.js,dropdown.min.js,nav.js&1468261673

b=js&f=jquery-1.10.2.min.js,jquery-migrate-1.2.1.min.js,tooltip_v5.js,main.js,dropdown.min.js,nav.js&1468261673

1688 ms

jquery.sumoselect.min.js&1492409085

jquery.sumoselect.min.js&1492409085

1688 ms

jquery.impromptu-3.3.3.js&1470252008

jquery.impromptu-3.3.3.js&1470252008

1688 ms

jquery.bgiframe.min.js&1468261673

jquery.bgiframe.min.js&1468261673

1686 ms

jquery-ui.js&1468261673

jquery-ui.js&1468261673

1687 ms

jquery.autocomplete.js&1498828734

jquery.autocomplete.js&1498828734

1687 ms

buttons.js&1488408298

buttons.js&1488408298

1746 ms

nav_2017.js&1504576983

nav_2017.js&1504576983

1638 ms

thickbox-compressed.js&1468261673

thickbox-compressed.js&1468261673

1429 ms

js_ptc.js&1468261673

js_ptc.js&1468261673

1262 ms

bootstrap.min.js

bootstrap.min.js

2593 ms

fbevents.js

fbevents.js

2747 ms

css

css

2618 ms

1648604235453166

1648604235453166

557 ms

870 ms

secureAnonymousFramework

secureAnonymousFramework

2511 ms

gpt.js

gpt.js

2231 ms

2163 ms

pubads_impl_147.js

pubads_impl_147.js

652 ms

1119374_r4a9ab7994f840.jpg

1119374_r4a9ab7994f840.jpg

477 ms

27266_r597f78e3214f4.jpg

27266_r597f78e3214f4.jpg

386 ms

64665_r4d3468f2a7af9.jpg

64665_r4d3468f2a7af9.jpg

385 ms

proz-header-logo-sm.png

proz-header-logo-sm.png

386 ms

729739_r57e5655354220.jpg

729739_r57e5655354220.jpg

333 ms

ptc_logo_small_v1_sm.gif

ptc_logo_small_v1_sm.gif

333 ms

1245248_r4db6e6050fe3c.jpg

1245248_r4db6e6050fe3c.jpg

332 ms

icon-pro-tag-lrg.png

icon-pro-tag-lrg.png

323 ms

tm-town-logo-142-37.png

tm-town-logo-142-37.png

389 ms

plat_tiny_trans.gif

plat_tiny_trans.gif

387 ms

sdk.js

sdk.js

387 ms

widgets.js

widgets.js

2081 ms

ga.js

ga.js

339 ms

proz-logo-shadowed.svg

proz-logo-shadowed.svg

1147 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

8004 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

7947 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

7947 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

7943 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

7941 ms

fontcustom_bbd6c977c958cdd46d4114a2538c488b.svg

fontcustom_bbd6c977c958cdd46d4114a2538c488b.svg

7941 ms

fontcustom_bbd6c977c958cdd46d4114a2538c488b.woff

fontcustom_bbd6c977c958cdd46d4114a2538c488b.woff

6182 ms

icon-plus.png

icon-plus.png

6179 ms

container.html

container.html

6302 ms

__utm.gif

__utm.gif

3673 ms

icon-fat-id.png

icon-fat-id.png

808 ms

icon-tack.png

icon-tack.png

807 ms

icon-info.png

icon-info.png

1019 ms

trans_ul_corner.gif

trans_ul_corner.gif

2362 ms

trans_ur_corner.gif

trans_ur_corner.gif

2362 ms

trans_ur_corner.gif

trans_ur_corner.gif

2363 ms

trans_ul_corner.gif

trans_ul_corner.gif

2362 ms

trans_lr_corner.gif

trans_lr_corner.gif

2422 ms

trans_ll_corner.gif

trans_ll_corner.gif

2421 ms

ads

ads

1881 ms

arrow-down-teal.gif

arrow-down-teal.gif

1690 ms

1493 ms

648 ms

0sTQzbapM8j.js

0sTQzbapM8j.js

1832 ms

0sTQzbapM8j.js

0sTQzbapM8j.js

3444 ms

proz-ideas-bg.png

proz-ideas-bg.png

435 ms

globe.jpg

globe.jpg

162 ms

loadingAnimation.gif

loadingAnimation.gif

5310 ms

share

share

5475 ms

sprite_connect_v14.png

sprite_connect_v14.png

7616 ms

button.3ccb64e61d4c01fae12cd2b0ed9b2bab.js

button.3ccb64e61d4c01fae12cd2b0ed9b2bab.js

1390 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

487 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

1250 ms

fastbutton

fastbutton

1423 ms

loadingAnimation.gif

loadingAnimation.gif

2804 ms

like.php

like.php

1369 ms

rs=AGLTcCOnDxwX8-LbpDmaxOBIoHm7W_kGNA

rs=AGLTcCOnDxwX8-LbpDmaxOBIoHm7W_kGNA

1701 ms

0zf7krTbbuX.js

0zf7krTbbuX.js

3497 ms

lH1ibRl5GKq.png

lH1ibRl5GKq.png

3579 ms

postmessageRelay

postmessageRelay

3733 ms

tweet_button.f8c8d971a6ac545cf416e3c1ad4bbc65.en.html

tweet_button.f8c8d971a6ac545cf416e3c1ad4bbc65.en.html

892 ms

jot

jot

1985 ms

jot

jot

716 ms

971028622-postmessagerelay.js

971028622-postmessagerelay.js

573 ms

rpc:shindig_random.js

rpc:shindig_random.js

356 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

15 ms

Accessibility Review

proz.com accessibility score

96

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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.

Best Practices

proz.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

proz.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

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

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 Proz.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 Proz.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

proz.com

Open Graph description is not detected on the main page of ProZ. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: