Tools & Wizards About Us
hpm.news screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

hpm.news

HPM App Server

Page Load Speed

3 sec in total

First Response

162 ms

Resources Loaded

1.4 sec

Page Rendered

1.4 sec

hpm.news screenshot

About Website

Welcome to hpm.news homepage info - get ready to check HPM best content right away, or after learning these important things about hpm.news

Hello, Houston Newsletter Signup Hello, Houston! is our free daily newsletter sent directly to your inbox. Let the Houston Public Media newsroom help you start your day, with the deep-dive reporting t...

Visit hpm.news

Key Findings

We analyzed Hpm.news page load time and found that the first response time was 162 ms and then it took 2.8 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

hpm.news performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value5,300 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value19.4 s

2/100

10%

Network Requests Diagram

hpm.news

162 ms

508 ms

gtm.js

127 ms

gtm.js

209 ms

wpforms-full.min.css

220 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Hpm.news, 20% (7 requests) were made to Cdn.houstonpublicmedia.org and 17% (6 requests) were made to Houstonpublicmedia.org. The less responsive or slowest element that took the longest time to load (508 ms) relates to the external source Houstonpublicmedia.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 131.0 kB (17%)

Content Size

765.4 kB

After Optimization

634.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hpm.news main page is 765.4 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. 40% of websites need less resources to load. Images take 287.1 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 97.8 kB

  • Original 122.0 kB
  • After minification 115.5 kB
  • After compression 24.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 97.8 kB or 80% of the original size.

Image Optimization

-10%

Potential reduce by 29.2 kB

  • Original 287.1 kB
  • After minification 257.8 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

-0%

Potential reduce by 209 B

  • Original 285.8 kB
  • After minification 285.8 kB
  • After compression 285.6 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

-5%

Potential reduce by 3.8 kB

  • Original 70.5 kB
  • After minification 70.5 kB
  • After compression 66.7 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.news has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 16 (52%)

Requests Now

31

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 31 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 13 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

hpm.news

hpm.news

162 ms

508 ms

gtm.js

gtm.js

127 ms

gtm.js

gtm.js

209 ms

wpforms-full.min.css

wpforms-full.min.css

220 ms

bootstrap.min.css

bootstrap.min.css

82 ms

style.css

style.css

263 ms

jquery.min.js

jquery.min.js

222 ms

jquery-migrate.min.js

jquery-migrate.min.js

96 ms

gpt.js

gpt.js

104 ms

hls.js@latest

hls.js@latest

33 ms

jppIframe.js

jppIframe.js

185 ms

fonts.css

fonts.css

109 ms

webforms.min.js

webforms.min.js

84 ms

bootstrap.min.js

bootstrap.min.js

234 ms

main.js

main.js

233 ms

css2

css2

40 ms

01n@2x.png

01n@2x.png

297 ms

houston-public-media-logo.png

houston-public-media-logo.png

55 ms

icon-listen.png

icon-listen.png

56 ms

icon-watch.png

icon-watch.png

54 ms

icon-donate.png

icon-donate.png

61 ms

Hello-Houston_Newsletter_Header.png.webp

Hello-Houston_Newsletter_Header.png.webp

406 ms

pubads_impl.js

pubads_impl.js

45 ms

ppub_config

ppub_config

110 ms

css

css

219 ms

ads

ads

70 ms

container.html

container.html

28 ms

font

font

122 ms

2266221108049570609

2266221108049570609

109 ms

window_focus.js

window_focus.js

112 ms

ads

ads

123 ms

ads

ads

115 ms

ml_jQuery.inputmask.bundle.min.js

ml_jQuery.inputmask.bundle.min.js

113 ms

11549888693021965465

11549888693021965465

20 ms

Accessibility Review

hpm.news accessibility score

89

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

hpm.news best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Page has valid source maps

SEO Factors

hpm.news 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.news 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.news 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

hpm.news

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: