Tools & Wizards About Us
wjaa.net screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

wjaa.net

96.3 WJAA - Where Indiana Rocks

Page Load Speed

1.8 sec in total

First Response

211 ms

Resources Loaded

968 ms

Page Rendered

604 ms

wjaa.net screenshot

About Website

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

Total Rock Radio at WJAA 96.3

Visit wjaa.net

Key Findings

We analyzed Wjaa.net page load time and found that the first response time was 211 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

wjaa.net performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

80/100

25%

SI (Speed Index)

Value3.5 s

88/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.364

29/100

15%

TTI (Time to Interactive)

Value6.6 s

58/100

10%

Network Requests Diagram

wjaa.net

211 ms

unite-gallery.css

90 ms

content.css

18 ms

nexus.min.css

55 ms

responsive.min.css

54 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 90% of them (63 requests) were addressed to the original Wjaa.net, 4% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (290 ms) belongs to the original domain Wjaa.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 216.6 kB (8%)

Content Size

2.8 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wjaa.net main page is 2.8 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. 70% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 27.4 kB

  • Original 35.4 kB
  • After minification 34.1 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. 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 27.4 kB or 77% of the original size.

Image Optimization

-7%

Potential reduce by 178.2 kB

  • Original 2.5 MB
  • After minification 2.4 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. WJAA images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 749 B

  • Original 129.7 kB
  • After minification 129.7 kB
  • After compression 128.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.

CSS Optimization

-15%

Potential reduce by 10.3 kB

  • Original 69.8 kB
  • After minification 69.8 kB
  • After compression 59.5 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. Wjaa.net needs all CSS files to be minified and compressed as it can save up to 10.3 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (36%)

Requests Now

66

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wjaa.net

wjaa.net

211 ms

unite-gallery.css

unite-gallery.css

90 ms

content.css

content.css

18 ms

nexus.min.css

nexus.min.css

55 ms

responsive.min.css

responsive.min.css

54 ms

css

css

69 ms

css

css

75 ms

jquery.min.js

jquery.min.js

70 ms

jquery-noconflict.js

jquery-noconflict.js

69 ms

jquery-migrate.min.js

jquery-migrate.min.js

69 ms

unitegallery.min.js

unitegallery.min.js

126 ms

ug-theme-tiles.js

ug-theme-tiles.js

104 ms

caption.js

caption.js

68 ms

core.js

core.js

70 ms

bootstrap.min.js

bootstrap.min.js

69 ms

mmenu-light.js

mmenu-light.js

70 ms

noframework.waypoints.min.js

noframework.waypoints.min.js

69 ms

jarallax.min.js

jarallax.min.js

73 ms

scripts.js

scripts.js

81 ms

js

js

68 ms

gtm.js

gtm.js

166 ms

Logo145.png

Logo145.png

165 ms

GalleryImages-01_300x100000.png

GalleryImages-01_300x100000.png

77 ms

GalleryImages-04_300x100000.png

GalleryImages-04_300x100000.png

89 ms

GalleryImages-05_300x100000.png

GalleryImages-05_300x100000.png

57 ms

GalleryImages-06_300x100000.png

GalleryImages-06_300x100000.png

104 ms

GalleryImages-07_300x100000.png

GalleryImages-07_300x100000.png

79 ms

GalleryImages-08_300x100000.png

GalleryImages-08_300x100000.png

135 ms

GalleryImages-09_300x100000.png

GalleryImages-09_300x100000.png

135 ms

GalleryImages-10_300x100000.png

GalleryImages-10_300x100000.png

77 ms

GalleryImages-11_300x100000.png

GalleryImages-11_300x100000.png

88 ms

cover-grid.png

cover-grid.png

89 ms

loader_skype_trans.gif

loader_skype_trans.gif

102 ms

lightbox-icon-close.png

lightbox-icon-close.png

100 ms

lightbox-arrow-left.png

lightbox-arrow-left.png

103 ms

lightbox-arrow-right.png

lightbox-arrow-right.png

123 ms

loader-black3.gif

loader-black3.gif

130 ms

play-button-square.png

play-button-square.png

124 ms

loader-black1.gif

loader-black1.gif

129 ms

GalleryImages-01.png

GalleryImages-01.png

130 ms

GalleryImages-04.png

GalleryImages-04.png

151 ms

GalleryImages-11.png

GalleryImages-11.png

162 ms

Logo100.png

Logo100.png

32 ms

StreamButton.png

StreamButton.png

33 ms

Facebook.png

Facebook.png

34 ms

EmailButton.png

EmailButton.png

33 ms

Lolas.png

Lolas.png

85 ms

GraphicButton-FinallyFriday.png

GraphicButton-FinallyFriday.png

72 ms

PizzaWednesday.png

PizzaWednesday.png

56 ms

Interview-Button.png

Interview-Button.png

71 ms

QuestionDay.png

QuestionDay.png

72 ms

JacksonRecy-StreamingSponsors.png

JacksonRecy-StreamingSponsors.png

74 ms

Calvary.png

Calvary.png

82 ms

TumblerCure.png

TumblerCure.png

86 ms

CancerCandle.png

CancerCandle.png

96 ms

flowerlinebreak.png

flowerlinebreak.png

84 ms

S-Wilson-Jr.png

S-Wilson-Jr.png

129 ms

CoomerClosingsLogo.png

CoomerClosingsLogo.png

118 ms

wjaa.net

wjaa.net

290 ms

WJAA-Advertise-Button.png

WJAA-Advertise-Button.png

97 ms

750-EnchantedForest_Banners.png

750-EnchantedForest_Banners.png

146 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

65 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

74 ms

N0bV2SdQO-5yM0-dGlNQIQ.ttf

N0bV2SdQO-5yM0-dGlNQIQ.ttf

76 ms

animate.min.css

animate.min.css

86 ms

fontawesome.min.css

fontawesome.min.css

87 ms

v4-shims.min.css

v4-shims.min.css

93 ms

brands.min.css

brands.min.css

94 ms

regular.min.css

regular.min.css

95 ms

solid.min.css

solid.min.css

104 ms

Accessibility Review

wjaa.net accessibility score

95

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.

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

Links do not have a discernible name

Best Practices

wjaa.net best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

wjaa.net SEO score

100

Search Engine Optimization Advices

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

wjaa.net

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