Tools & Wizards About Us
worldpressphoto.org screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

worldpressphoto.org

Home | World Press Photo

Page Load Speed

59.6 sec in total

First Response

494 ms

Resources Loaded

15.8 sec

Page Rendered

43.3 sec

worldpressphoto.org screenshot

About Website

Welcome to worldpressphoto.org homepage info - get ready to check World Press Photo best content for United States right away, or after learning these important things about worldpressphoto.org

Connecting the world to the stories that matter.

Visit worldpressphoto.org

Key Findings

We analyzed Worldpressphoto.org page load time and found that the first response time was 494 ms and then it took 59.1 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

worldpressphoto.org performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value650 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value1.186

1/100

15%

TTI (Time to Interactive)

Value4.4 s

83/100

10%

Network Requests Diagram

worldpressphoto.org

494 ms

www.worldpressphoto.org

437 ms

www.worldpressphoto.org

999 ms

css_kShW4RPmRstZ3SpIC-ZvVGNFVAi0WEMuCnI0ZkYIaFw.css

191 ms

css_GXQ4lgzYKqUYNSdqiJU5OeHuHqXuV78thhb6c079lvc.css

431 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 98% of them (50 requests) were addressed to the original Worldpressphoto.org, 2% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Worldpressphoto.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 6.7 MB (24%)

Content Size

28.1 MB

After Optimization

21.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Worldpressphoto.org main page is 28.1 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 21.3 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 38.6 kB

  • Original 46.5 kB
  • After minification 33.6 kB
  • After compression 8.0 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.0 kB, which is 28% 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 38.6 kB or 83% of the original size.

Image Optimization

-9%

Potential reduce by 2.0 MB

  • Original 21.3 MB
  • After minification 19.3 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. World Press Photo images are well optimized though.

JavaScript Optimization

-79%

Potential reduce by 3.0 MB

  • Original 3.9 MB
  • After minification 3.0 MB
  • After compression 830.2 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 3.0 MB or 79% of the original size.

CSS Optimization

-58%

Potential reduce by 1.6 MB

  • Original 2.8 MB
  • After minification 2.7 MB
  • After compression 1.2 MB

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. Worldpressphoto.org needs all CSS files to be minified and compressed as it can save up to 1.6 MB or 58% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (37%)

Requests Now

43

After Optimization

27

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

worldpressphoto.org

worldpressphoto.org

494 ms

www.worldpressphoto.org

www.worldpressphoto.org

437 ms

www.worldpressphoto.org

www.worldpressphoto.org

999 ms

css_kShW4RPmRstZ3SpIC-ZvVGNFVAi0WEMuCnI0ZkYIaFw.css

css_kShW4RPmRstZ3SpIC-ZvVGNFVAi0WEMuCnI0ZkYIaFw.css

191 ms

css_GXQ4lgzYKqUYNSdqiJU5OeHuHqXuV78thhb6c079lvc.css

css_GXQ4lgzYKqUYNSdqiJU5OeHuHqXuV78thhb6c079lvc.css

431 ms

css_-r90eZ3v_5ZVRlo8ThNt1G-Kb5hEUixjXcpNqx_oyU0.css

css_-r90eZ3v_5ZVRlo8ThNt1G-Kb5hEUixjXcpNqx_oyU0.css

790 ms

css_HqAXdUE3zrIVqpLfk3qRRVYJ7nBW4Q2J-7jCgEragmA.css

css_HqAXdUE3zrIVqpLfk3qRRVYJ7nBW4Q2J-7jCgEragmA.css

1010 ms

css_o00MBN9AfjIqRwiVxSTIk8t17UzoyuMBI83xHqv__Po.css

css_o00MBN9AfjIqRwiVxSTIk8t17UzoyuMBI83xHqv__Po.css

853 ms

css_kV5L2xkTYi5De7_uAl-wyEgv_MP-CSHp9Z5FO_rk_ao.css

css_kV5L2xkTYi5De7_uAl-wyEgv_MP-CSHp9Z5FO_rk_ao.css

1109 ms

css_7gVl_6qSLeoOhycShsGZ8lvnQaaRzo6qVkdAs1behc4.css

css_7gVl_6qSLeoOhycShsGZ8lvnQaaRzo6qVkdAs1behc4.css

980 ms

css_wGG_tmwd-_priZfkPxfLMdxw5J9uyosKeYCQLP3IKx8.css

css_wGG_tmwd-_priZfkPxfLMdxw5J9uyosKeYCQLP3IKx8.css

1046 ms

css_t8FGMJEC7KDQuKtIIfzmD6zy-8RMg-U5K1hR_zhreoY.css

css_t8FGMJEC7KDQuKtIIfzmD6zy-8RMg-U5K1hR_zhreoY.css

1101 ms

css_LfMto7SMVVjFO6u9ntr1miSrK04zp8Rh3K-vU2AAjGs.css

css_LfMto7SMVVjFO6u9ntr1miSrK04zp8Rh3K-vU2AAjGs.css

1102 ms

js_Gz-4LKmWDkhFJLJEfT2bKrK-dh5Mh1DjUmTWd3tyl6k.js

js_Gz-4LKmWDkhFJLJEfT2bKrK-dh5Mh1DjUmTWd3tyl6k.js

1260 ms

js_NpX2cwCeepkWZZ194B6-ViyVBHleaYLOx5R9EWBOMRU.js

js_NpX2cwCeepkWZZ194B6-ViyVBHleaYLOx5R9EWBOMRU.js

1085 ms

js_301QHPsNmG-MTJNih5gOe2VCoTI5eT98aqsdIjJn57w.js

js_301QHPsNmG-MTJNih5gOe2VCoTI5eT98aqsdIjJn57w.js

1956 ms

js_NFdBn--IsfdcY5E2W7xVsCP3v42vi4iGWHQF9DqNtrg.js

js_NFdBn--IsfdcY5E2W7xVsCP3v42vi4iGWHQF9DqNtrg.js

1178 ms

js_diWL3aQY3h6RRBatVIE0RJfaXsBie-hoJ861ArHzvB0.js

js_diWL3aQY3h6RRBatVIE0RJfaXsBie-hoJ861ArHzvB0.js

1178 ms

js_fIpKDJPCzgApzsVHPfa7cdWPu0FGXXaI0tlkkWevC5o.js

js_fIpKDJPCzgApzsVHPfa7cdWPu0FGXXaI0tlkkWevC5o.js

1177 ms

logo.png

logo.png

401 ms

header-bg.png

header-bg.png

102 ms

footer-search.png

footer-search.png

102 ms

wpphyear.jpg

wpphyear.jpg

367 ms

01_11.jpg

01_11.jpg

2787 ms

zybnqrpgs8ndwsdfylvk.jpg

zybnqrpgs8ndwsdfylvk.jpg

2787 ms

MARCH.JPG

MARCH.JPG

3008 ms

see-the-story-2.jpg

see-the-story-2.jpg

2759 ms

jaime-rojo_0.png

jaime-rojo_0.png

3401 ms

instagram-logo.jpg

instagram-logo.jpg

2759 ms

cameron-spencer-4.png

cameron-spencer-4.png

3101 ms

cameron-spencer-2.png

cameron-spencer-2.png

2921 ms

cameron-spencer-1.png

cameron-spencer-1.png

2923 ms

cameron-spencer-3.png

cameron-spencer-3.png

3080 ms

WPP_Witness_logo_182x70px.png

WPP_Witness_logo_182x70px.png

2922 ms

through-a-glass-darkly.png

through-a-glass-darkly.png

3081 ms

four-to-follow-2.png

four-to-follow-2.png

3668 ms

creative-treatments-of-actuality.png

creative-treatments-of-actuality.png

3564 ms

turn-the-cameras-on-the-architecture-of-exclusion-in-calais.png

turn-the-cameras-on-the-architecture-of-exclusion-in-calais.png

3566 ms

NPL_high@2x.png

NPL_high@2x.png

3264 ms

Canon_high@2x.png

Canon_high@2x.png

3236 ms

fb-footer@2x.png

fb-footer@2x.png

3237 ms

tweet-footer@2x.png

tweet-footer@2x.png

3236 ms

sponsor_acquia_adj@2x.png

sponsor_acquia_adj@2x.png

3356 ms

emakina-logo.png

emakina-logo.png

3356 ms

akkurat-wpp-pro-light.woff

akkurat-wpp-pro-light.woff

4671 ms

akkurat-wpp-pro-bold.woff

akkurat-wpp-pro-bold.woff

4671 ms

wpph-icons.woff

wpph-icons.woff

3902 ms

wpph-icons.woff

wpph-icons.woff

3901 ms

akkurat-wpp-pro-regular.woff

akkurat-wpp-pro-regular.woff

4670 ms

analytics.js

analytics.js

4668 ms

css_7MH1Mdp_QKSeeOf9PJS6xNcQB5TFoStZQMRqu7tI_Q8.css

css_7MH1Mdp_QKSeeOf9PJS6xNcQB5TFoStZQMRqu7tI_Q8.css

1007 ms

Accessibility Review

worldpressphoto.org accessibility score

74

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

worldpressphoto.org best practices score

92

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

Page has valid source maps

SEO Factors

worldpressphoto.org SEO score

92

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

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 Worldpressphoto.org 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 Worldpressphoto.org 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

worldpressphoto.org

Open Graph description is not detected on the main page of World Press Photo. 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: