Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

presson.com

PressReader.com - Digital Newspaper & Magazine Subscriptions

Page Load Speed

848 ms in total

First Response

142 ms

Resources Loaded

612 ms

Page Rendered

94 ms

presson.com screenshot

About Website

Welcome to presson.com homepage info - get ready to check Press On best content right away, or after learning these important things about presson.com

Digital newsstand featuring 7000+ of the world’s most popular newspapers & magazines. Enjoy unlimited reading on up to 5 devices with 7-day free trial.

Visit presson.com

Key Findings

We analyzed Presson.com page load time and found that the first response time was 142 ms and then it took 706 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

presson.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value15.8 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value3,630 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value15.3 s

7/100

10%

Network Requests Diagram

www.pressreader.com

142 ms

WebResource.ashx

37 ms

es6-shim.min.js

25 ms

app.build.min.js

64 ms

WebResource.ashx

25 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Presson.com, 22% (2 requests) were made to Fonts.gstatic.com and 11% (1 request) were made to Pressreader.com. The less responsive or slowest element that took the longest time to load (142 ms) relates to the external source Pressreader.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 14.8 kB (3%)

Content Size

552.6 kB

After Optimization

537.8 kB

In fact, the total size of Presson.com main page is 552.6 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. Only 10% of websites need less resources to load. Javascripts take 535.7 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 11.0 kB

  • Original 16.9 kB
  • After minification 16.2 kB
  • After compression 5.9 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 11.0 kB or 65% of the original size.

JavaScript Optimization

-1%

Potential reduce by 3.8 kB

  • Original 535.7 kB
  • After minification 535.7 kB
  • After compression 531.9 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.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Press On. According to our analytics all requests are already optimized.

Accessibility Review

presson.com accessibility score

89

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

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

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

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

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