Tools & Wizards About Us
nepm.org screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

nepm.org

NEPM | PBS, NPR and local perspective for western Mass. | New England Public Media

Page Load Speed

1.9 sec in total

First Response

245 ms

Resources Loaded

1.3 sec

Page Rendered

282 ms

nepm.org screenshot

About Website

Click here to check amazing NEPM content for United States. Otherwise, check out these important facts you probably never knew about nepm.org

New England Public Media endeavors to share new voices and inspire new conversations through a deep commitment to independent local journalism, trusted educational content, inspired cultural offerings...

Visit nepm.org

Key Findings

We analyzed Nepm.org page load time and found that the first response time was 245 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

nepm.org performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value1,190 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

nepm.org

245 ms

style.css

40 ms

jquery.min.js

156 ms

mh.js

69 ms

in.js

37 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 19% of them (9 requests) were addressed to the original Nepm.org, 17% (8 requests) were made to Apis.google.com and 15% (7 requests) were made to Secure.assets.tumblr.com. The less responsive or slowest element that took the longest time to load (557 ms) relates to the external source Media.line.me.

Page Optimization Overview & Recommendations

Page size can be reduced by 362.4 kB (21%)

Content Size

1.7 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nepm.org main page is 1.7 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. 45% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 15.5 kB

  • Original 20.9 kB
  • After minification 20.0 kB
  • After compression 5.3 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 15.5 kB or 74% of the original size.

Image Optimization

-1%

Potential reduce by 6.3 kB

  • Original 1.2 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. NEPM images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 318.3 kB

  • Original 518.3 kB
  • After minification 504.9 kB
  • After compression 200.0 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 318.3 kB or 61% of the original size.

CSS Optimization

-79%

Potential reduce by 22.3 kB

  • Original 28.1 kB
  • After minification 21.3 kB
  • After compression 5.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. Nepm.org needs all CSS files to be minified and compressed as it can save up to 22.3 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (60%)

Requests Now

47

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nepm.org

nepm.org

245 ms

style.css

style.css

40 ms

jquery.min.js

jquery.min.js

156 ms

mh.js

mh.js

69 ms

in.js

in.js

37 ms

line-button.js

line-button.js

557 ms

platform.js

platform.js

63 ms

bookmark_button.js

bookmark_button.js

554 ms

secureAnonymousFramework

secureAnonymousFramework

53 ms

button-only@2x.png

button-only@2x.png

424 ms

Main.jpg

Main.jpg

219 ms

Item2.jpg

Item2.jpg

170 ms

MainContentPhoto.jpg

MainContentPhoto.jpg

147 ms

Item3.jpg

Item3.jpg

247 ms

Item4.jpg

Item4.jpg

263 ms

sprite_connect_v14.png

sprite_connect_v14.png

146 ms

share-button.js

share-button.js

77 ms

btn.js

btn.js

71 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

17 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

42 ms

fastbutton

fastbutton

110 ms

463 ms

button

button

34 ms

postmessageRelay

postmessageRelay

61 ms

button.css

button.css

84 ms

shared.js

shared.js

83 ms

button.js

button.js

82 ms

button

button

161 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

22 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

20 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

44 ms

rpc:shindig_random.js

rpc:shindig_random.js

51 ms

pocket_button.png

pocket_button.png

8 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

3 ms

styles.css

styles.css

11 ms

rapid-3.36.js

rapid-3.36.js

28 ms

rapidworker-1.2.js

rapidworker-1.2.js

43 ms

index.js

index.js

53 ms

ga.js

ga.js

112 ms

analytics.js

analytics.js

108 ms

beacon.js

beacon.js

156 ms

impixu

impixu

171 ms

3d-t-button-blue.svg

3d-t-button-blue.svg

12 ms

__utm.gif

__utm.gif

31 ms

cedexis.radar.js

cedexis.radar.js

15 ms

reset.css

reset.css

16 ms

entry-button.css

entry-button.css

14 ms

bbtn-l_v3.png

bbtn-l_v3.png

3 ms

Accessibility Review

nepm.org accessibility score

97

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

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

High

Missing source maps for large first-party JavaScript

SEO Factors

nepm.org SEO score

91

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

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nepm.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Nepm.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

nepm.org

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