Report Summary

  • 21

    Performance

    Renders faster than
    40% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

hpm.io

Houston Public Media – Houston Public Media is a non-profit organization broadcasting through a multi-media platform to deliver content with a focus o...

Page Load Speed

6.4 sec in total

First Response

258 ms

Resources Loaded

3.9 sec

Page Rendered

2.2 sec

hpm.io screenshot

About Website

Click here to check amazing Hpm content for United States. Otherwise, check out these important facts you probably never knew about hpm.io

Houston Public Media provides informative, thought-provoking and entertaining content through a multi-media platform that includes TV 8, News 88.7 and HPM Classical and reaches a combined weekly audie...

Visit hpm.io

Key Findings

We analyzed Hpm.io page load time and found that the first response time was 258 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

hpm.io performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value6.1 s

44/100

10%

TBT (Total Blocking Time)

Value2,760 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.189

65/100

15%

TTI (Time to Interactive)

Value14.8 s

8/100

10%

Network Requests Diagram

hpm.io

258 ms

www.houstonpublicmedia.org

123 ms

gtm.js

345 ms

style.min.css

292 ms

style.css

299 ms

Our browser made a total of 116 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Hpm.io, 34% (40 requests) were made to Cdn.hpm.io and 14% (16 requests) were made to Msb.rphelios.net. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Media.npr.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 946.2 kB (46%)

Content Size

2.0 MB

After Optimization

1.1 MB

In fact, the total size of Hpm.io main page is 2.0 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. 85% 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 758.5 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 289.0 kB

  • Original 347.4 kB
  • After minification 289.9 kB
  • After compression 58.4 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 57.5 kB, which is 17% 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 289.0 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 12.1 kB

  • Original 758.5 kB
  • After minification 746.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. Hpm images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 319.4 kB

  • Original 549.7 kB
  • After minification 501.8 kB
  • After compression 230.3 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 319.4 kB or 58% of the original size.

CSS Optimization

-85%

Potential reduce by 325.7 kB

  • Original 383.6 kB
  • After minification 333.0 kB
  • After compression 57.9 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. Hpm.io needs all CSS files to be minified and compressed as it can save up to 325.7 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (50%)

Requests Now

102

After Optimization

51

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

Accessibility Review

hpm.io accessibility score

85

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-hidden="true"] elements contain focusable descendents

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

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

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

hpm.io best practices score

92

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

Page has valid source maps

SEO Factors

hpm.io 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 Hpm.io 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 Hpm.io 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 Hpm. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: