Tools & Wizards About Us
wsou.net screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

wsou.net

WSOU Index Page

Page Load Speed

1 sec in total

First Response

51 ms

Resources Loaded

772 ms

Page Rendered

185 ms

wsou.net screenshot

About Website

Welcome to wsou.net homepage info - get ready to check WSOU best content for United States right away, or after learning these important things about wsou.net

The loudest rock in New Jersey and NYC since 1986. Listen live, see playlists, events, and more from WSOU 89.5 FM.

Visit wsou.net

Key Findings

We analyzed Wsou.net page load time and found that the first response time was 51 ms and then it took 957 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

wsou.net performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value14.5 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value2,800 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.399

25/100

15%

TTI (Time to Interactive)

Value29.4 s

0/100

10%

Network Requests Diagram

wsou.net

51 ms

www.wsou.net

243 ms

wsou.css

12 ms

calendar.css

12 ms

socialmedia.css

14 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 70% of them (46 requests) were addressed to the original Wsou.net, 8% (5 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (253 ms) relates to the external source Cdn.syndication.twimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 718.3 kB (49%)

Content Size

1.5 MB

After Optimization

737.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wsou.net main page is 1.5 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. 65% of websites need less resources to load. Images take 549.6 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 147.4 kB

  • Original 200.5 kB
  • After minification 194.0 kB
  • After compression 53.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 147.4 kB or 74% of the original size.

Image Optimization

-4%

Potential reduce by 21.3 kB

  • Original 549.6 kB
  • After minification 528.3 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. WSOU images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 342.7 kB

  • Original 470.8 kB
  • After minification 381.0 kB
  • After compression 128.1 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 342.7 kB or 73% of the original size.

CSS Optimization

-88%

Potential reduce by 206.9 kB

  • Original 234.9 kB
  • After minification 165.2 kB
  • After compression 28.0 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. Wsou.net needs all CSS files to be minified and compressed as it can save up to 206.9 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (72%)

Requests Now

58

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wsou.net

wsou.net

51 ms

www.wsou.net

www.wsou.net

243 ms

wsou.css

wsou.css

12 ms

calendar.css

calendar.css

12 ms

socialmedia.css

socialmedia.css

14 ms

browser-all.js

browser-all.js

15 ms

css

css

25 ms

megamenu.css

megamenu.css

16 ms

megamenu.js

megamenu.js

15 ms

foundation.css

foundation.css

20 ms

modernizr.js

modernizr.js

15 ms

main.css

main.css

16 ms

commonspot.css

commonspot.css

14 ms

always-include-common.js

always-include-common.js

15 ms

brand

brand

19 ms

foundation.min.js

foundation.min.js

16 ms

google-analytics.js

google-analytics.js

13 ms

formstack-tracking.js

formstack-tracking.js

14 ms

facebook-tracking.js

facebook-tracking.js

15 ms

jquery-1.11.js

jquery-1.11.js

13 ms

brand

brand

61 ms

jquery-migrate-1.2.js

jquery-migrate-1.2.js

13 ms

fsa.js

fsa.js

125 ms

bg-fade.jpg

bg-fade.jpg

77 ms

Starland-Web-Banner.jpeg

Starland-Web-Banner.jpeg

73 ms

wsou.png

wsou.png

78 ms

iheart.png

iheart.png

77 ms

bg-dropdown.png

bg-dropdown.png

73 ms

icon-search.png

icon-search.png

74 ms

30years2_HL_resize.png

30years2_HL_resize.png

79 ms

showannouncement1.jpg

showannouncement1.jpg

79 ms

exclusives.jpg

exclusives.jpg

75 ms

spinitron.jpg

spinitron.jpg

111 ms

stream.jpg

stream.jpg

77 ms

shu.png

shu.png

79 ms

vintagetshirt_2.jpg

vintagetshirt_2.jpg

112 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

70 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

72 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

74 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

74 ms

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

73 ms

widgets.js

widgets.js

67 ms

analytics.js

analytics.js

57 ms

fbevents.js

fbevents.js

91 ms

util.js

util.js

51 ms

bg-slider.png

bg-slider.png

43 ms

social-sprite.png

social-sprite.png

45 ms

util.js

util.js

34 ms

buttons.css

buttons.css

33 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

34 ms

linkid.js

linkid.js

25 ms

buttons.css

buttons.css

30 ms

lightbox.css

lightbox.css

29 ms

113 ms

pageview

pageview

58 ms

collect

collect

15 ms

collect

collect

66 ms

syndication

syndication

90 ms

397634963773726720

397634963773726720

253 ms

lightbox.css

lightbox.css

20 ms

lightbox.js

lightbox.js

37 ms

lightbox.js

lightbox.js

11 ms

overrides.js

overrides.js

8 ms

overrides.js

overrides.js

12 ms

window_ref.js

window_ref.js

9 ms

window_ref.js

window_ref.js

8 ms

Accessibility Review

wsou.net accessibility score

68

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

wsou.net best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

wsou.net SEO score

83

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

wsou.net

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