Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

wgna.com

107.7 WGNA – Albany’s #1 For New Country – Albany Country Radio

Page Load Speed

3.2 sec in total

First Response

92 ms

Resources Loaded

1.2 sec

Page Rendered

1.9 sec

wgna.com screenshot

About Website

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

107.7 WGNA radio, a Townsquare Media station, plays the best country music in Albany, New York.

Visit wgna.com

Key Findings

We analyzed Wgna.com page load time and found that the first response time was 92 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

wgna.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

39/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value9,360 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.078

95/100

15%

TTI (Time to Interactive)

Value35.9 s

0/100

10%

Network Requests Diagram

wgna.com

92 ms

wgna.com

120 ms

base.css

70 ms

osano.js

42 ms

css

60 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 7% of them (5 requests) were addressed to the original Wgna.com, 38% (26 requests) were made to Townsquare.media and 10% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (513 ms) relates to the external source Invstatic101.creativecdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 230.7 kB (10%)

Content Size

2.3 MB

After Optimization

2.0 MB

In fact, the total size of Wgna.com main page is 2.3 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. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 194.1 kB

  • Original 241.2 kB
  • After minification 240.3 kB
  • After compression 47.2 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 194.1 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 3.6 kB

  • Original 1.6 MB
  • After minification 1.6 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. WGNA images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 33.0 kB

  • Original 418.5 kB
  • After minification 418.5 kB
  • After compression 385.4 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

Number of requests can be reduced by 18 (32%)

Requests Now

56

After Optimization

38

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

Accessibility Review

wgna.com accessibility score

71

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

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

High

<object> elements do not have alternate text

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

wgna.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the notification permission on page load

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

wgna.com SEO score

98

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

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 Wgna.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 Wgna.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 data is detected on the main page of WGNA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: