Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

pe.net

The Press-Enterprise: Local News, Sports and Things to Do

Page Load Speed

5.7 sec in total

First Response

341 ms

Resources Loaded

4.6 sec

Page Rendered

772 ms

pe.net screenshot

About Website

Click here to check amazing Pe content. Otherwise, check out these important facts you probably never knew about pe.net

The award-winning staff of PressEnterprise.com covers local news from Riverside County, CA, California and national news, sports, things to do, and business in the Inland Empire.

Visit pe.net

Key Findings

We analyzed Pe.net page load time and found that the first response time was 341 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

pe.net performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value14.4 s

0/100

25%

SI (Speed Index)

Value17.9 s

0/100

10%

TBT (Total Blocking Time)

Value6,720 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.326

35/100

15%

TTI (Time to Interactive)

Value32.5 s

0/100

10%

Network Requests Diagram

www.pe.net

341 ms

www.pe.com

480 ms

load.php

284 ms

load.php

135 ms

load.php

204 ms

Our browser made a total of 283 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Pe.net, 7% (20 requests) were made to Um.simpli.fi and 6% (16 requests) were made to Images.onset.freedom.com. The less responsive or slowest element that took the longest time to load (658 ms) relates to the external source Ybrant.appserver.tv.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (45%)

Content Size

3.6 MB

After Optimization

2.0 MB

In fact, the total size of Pe.net main page is 3.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. 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 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 152.8 kB

  • Original 203.9 kB
  • After minification 198.6 kB
  • After compression 51.1 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 152.8 kB or 75% of the original size.

Image Optimization

-6%

Potential reduce by 77.8 kB

  • Original 1.3 MB
  • After minification 1.2 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. Pe images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 1.3 MB

  • Original 2.0 MB
  • After minification 2.0 MB
  • After compression 712.7 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 1.3 MB or 64% of the original size.

CSS Optimization

-82%

Potential reduce by 123.5 kB

  • Original 149.8 kB
  • After minification 112.6 kB
  • After compression 26.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. Pe.net needs all CSS files to be minified and compressed as it can save up to 123.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 159 (69%)

Requests Now

232

After Optimization

73

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

Accessibility Review

pe.net accessibility score

83

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-*] attributes do not match their roles

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

pe.net best practices score

83

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

Browser errors were logged to the console

SEO Factors

pe.net SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 Pe.net 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 Pe.net 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 Pe. 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: