Tools & Wizards About Us
player.htzfm.com screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

player.htzfm.com

97.7 HTZ-FM

Page Load Speed

885 ms in total

First Response

141 ms

Resources Loaded

644 ms

Page Rendered

100 ms

player.htzfm.com screenshot

About Website

Visit player.htzfm.com now to see the best up-to-date Player HTZ FM content for Canada and also check out these interesting facts you probably never knew about player.htzfm.com

97-7 HTZ FM is Southern Ontario’s Best rock, located in St. Catharines, ON, Canada. CHTZ-FM is part of iHeartRADIO

Visit player.htzfm.com

Key Findings

We analyzed Player.htzfm.com page load time and found that the first response time was 141 ms and then it took 744 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

player.htzfm.com performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value22.4 s

0/100

25%

SI (Speed Index)

Value16.5 s

0/100

10%

TBT (Total Blocking Time)

Value6,580 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.32

36/100

15%

TTI (Time to Interactive)

Value34.2 s

0/100

10%

Network Requests Diagram

player.htzfm.com

141 ms

jquery.min.js

23 ms

BrightcoveExperiences.js

13 ms

astralObj.js

187 ms

s_code.js

164 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 7% of them (1 request) were addressed to the original Player.htzfm.com, 29% (4 requests) were made to Proxy.amri.ca and 14% (2 requests) were made to Config.7821k.com. The less responsive or slowest element that took the longest time to load (285 ms) relates to the external source Astralcontent.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 410.0 kB (78%)

Content Size

524.2 kB

After Optimization

114.3 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Player.htzfm.com main page is 524.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Javascripts take 347.4 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 4.1 kB

  • Original 6.2 kB
  • After minification 5.4 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 747 B, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 4.1 kB or 66% of the original size.

JavaScript Optimization

-72%

Potential reduce by 251.5 kB

  • Original 347.4 kB
  • After minification 306.0 kB
  • After compression 95.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 251.5 kB or 72% of the original size.

CSS Optimization

-90%

Potential reduce by 154.4 kB

  • Original 170.6 kB
  • After minification 129.2 kB
  • After compression 16.2 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. Player.htzfm.com needs all CSS files to be minified and compressed as it can save up to 154.4 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (77%)

Requests Now

13

After Optimization

3

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

player.htzfm.com

player.htzfm.com

141 ms

jquery.min.js

jquery.min.js

23 ms

BrightcoveExperiences.js

BrightcoveExperiences.js

13 ms

astralObj.js

astralObj.js

187 ms

s_code.js

s_code.js

164 ms

player_load_scripts.js.php

player_load_scripts.js.php

81 ms

controltag

controltag

50 ms

jquery-ui-1.8.16.custom.css

jquery-ui-1.8.16.custom.css

27 ms

ludio_coverflip.css

ludio_coverflip.css

53 ms

css

css

25 ms

proxy.amri.ca

proxy.amri.ca

77 ms

tritonArray.js

tritonArray.js

285 ms

beacon2.dll

beacon2.dll

3 ms

controltag.js.f8e94fa978cc2569e4b4423df4245d7e

controltag.js.f8e94fa978cc2569e4b4423df4245d7e

60 ms

Accessibility Review

player.htzfm.com 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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

player.htzfm.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

player.htzfm.com SEO score

85

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Player.htzfm.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Player.htzfm.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

player.htzfm.com

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: