Tools & Wizards About Us
kttz.org screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

kttz.org

Texas Tech Public Media | NPR & PBS in West Texas

Page Load Speed

2.2 sec in total

First Response

45 ms

Resources Loaded

1.5 sec

Page Rendered

622 ms

kttz.org screenshot

About Website

Click here to check amazing Kttz content for United States. Otherwise, check out these important facts you probably never knew about kttz.org

Texas Tech Public Media serves as the PBS and NPR stations for Lubbock, the PBS station for El Paso, and the NPR station for San Angelo.

Visit kttz.org

Key Findings

We analyzed Kttz.org page load time and found that the first response time was 45 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

kttz.org performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value1,840 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.222

56/100

15%

TTI (Time to Interactive)

Value21.7 s

1/100

10%

Network Requests Diagram

kttz.org

45 ms

www.kttz.org

680 ms

gtm.js

77 ms

autoptimize_f5eeddf6d6ee1dd6e194d185fa5e9355.css

120 ms

autoptimize_single_5099594804dc8727336965f900d05d86.css

169 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 92% of them (54 requests) were addressed to the original Kttz.org, 2% (1 request) were made to Googletagmanager.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (680 ms) belongs to the original domain Kttz.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 711.2 kB (15%)

Content Size

4.9 MB

After Optimization

4.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kttz.org main page is 4.9 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. 65% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 72.5 kB

  • Original 91.1 kB
  • After minification 85.3 kB
  • After compression 18.6 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 72.5 kB or 80% of the original size.

Image Optimization

-6%

Potential reduce by 230.5 kB

  • Original 3.8 MB
  • After minification 3.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. Kttz images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 385.8 kB

  • Original 822.1 kB
  • After minification 815.1 kB
  • After compression 436.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 385.8 kB or 47% of the original size.

CSS Optimization

-17%

Potential reduce by 22.3 kB

  • Original 134.7 kB
  • After minification 134.7 kB
  • After compression 112.3 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. Kttz.org needs all CSS files to be minified and compressed as it can save up to 22.3 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (65%)

Requests Now

54

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kttz.org

kttz.org

45 ms

www.kttz.org

www.kttz.org

680 ms

gtm.js

gtm.js

77 ms

autoptimize_f5eeddf6d6ee1dd6e194d185fa5e9355.css

autoptimize_f5eeddf6d6ee1dd6e194d185fa5e9355.css

120 ms

autoptimize_single_5099594804dc8727336965f900d05d86.css

autoptimize_single_5099594804dc8727336965f900d05d86.css

169 ms

css

css

51 ms

autoptimize_single_d7db0ac4f7fccb30f70ad595708d4c81.css

autoptimize_single_d7db0ac4f7fccb30f70ad595708d4c81.css

61 ms

autoptimize_single_e4932344fa3365096f60b3000640504e.js

autoptimize_single_e4932344fa3365096f60b3000640504e.js

61 ms

jquery.min.js

jquery.min.js

87 ms

jquery-migrate.min.js

jquery-migrate.min.js

213 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

104 ms

autoptimize_single_45e001e9a476bc6aa8312923ee953b5a.css

autoptimize_single_45e001e9a476bc6aa8312923ee953b5a.css

209 ms

autoptimize_single_7826eeb04a5f0314397db8798ec77538.css

autoptimize_single_7826eeb04a5f0314397db8798ec77538.css

198 ms

autoptimize_single_07e3e5bebfd51391fdce8f22e2227f60.css

autoptimize_single_07e3e5bebfd51391fdce8f22e2227f60.css

196 ms

autoptimize_single_efc27e253fae1b7b891fb5a40e687768.js

autoptimize_single_efc27e253fae1b7b891fb5a40e687768.js

234 ms

autoptimize_single_917602d642f84a211838f0c1757c4dc1.js

autoptimize_single_917602d642f84a211838f0c1757c4dc1.js

196 ms

jquery.easing.min.js

jquery.easing.min.js

230 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

233 ms

autoptimize_single_b08178f9f045f881029f695e4b939291.js

autoptimize_single_b08178f9f045f881029f695e4b939291.js

233 ms

transit.min.js

transit.min.js

317 ms

autoptimize_single_900bad1dbd9b131a99f31703a66340f3.js

autoptimize_single_900bad1dbd9b131a99f31703a66340f3.js

235 ms

imagesLoaded.min.js

imagesLoaded.min.js

316 ms

hoverintent.min.js

hoverintent.min.js

325 ms

autoptimize_single_7270c88429fb55fdfed258cd32beb804.js

autoptimize_single_7270c88429fb55fdfed258cd32beb804.js

344 ms

anime.min.js

anime.min.js

349 ms

autoptimize_single_beca72584b7b6df68f09cd56acd813cc.js

autoptimize_single_beca72584b7b6df68f09cd56acd813cc.js

315 ms

autoptimize_single_a0356157d149b7bf1cf2ec157ae56e32.js

autoptimize_single_a0356157d149b7bf1cf2ec157ae56e32.js

319 ms

touchswipe.min.js

touchswipe.min.js

398 ms

api.js

api.js

61 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

416 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

400 ms

wp-polyfill.min.js

wp-polyfill.min.js

480 ms

autoptimize_single_ec0187677793456f98473f49d9e9b95f.js

autoptimize_single_ec0187677793456f98473f49d9e9b95f.js

478 ms

js_composer_front.min.js

js_composer_front.min.js

389 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

510 ms

autoptimize_single_e4b54a64a8453d855f8d21bce03d5814.js

autoptimize_single_e4b54a64a8453d855f8d21bce03d5814.js

475 ms

wpra-manifest.min.js

wpra-manifest.min.js

475 ms

pagination.min.js

pagination.min.js

476 ms

texas-tech-public-media-logo-wide.png

texas-tech-public-media-logo-wide.png

284 ms

web-banner-slide_.png

web-banner-slide_.png

380 ms

960x540-website-banner-revised.png

960x540-website-banner-revised.png

286 ms

news-with-morning-brews.jpg

news-with-morning-brews.jpg

438 ms

P2.png

P2.png

287 ms

web-banner.png

web-banner.png

528 ms

90-4.jpg

90-4.jpg

456 ms

90-2.png

90-2.png

425 ms

90-3.jpg

90-3.jpg

412 ms

90-2.jpg

90-2.jpg

380 ms

90-1.jpg

90-1.jpg

423 ms

90-1.png

90-1.png

495 ms

90.png

90.png

510 ms

90.jpg

90.jpg

449 ms

2068Charter-Book.woff

2068Charter-Book.woff

311 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

432 ms

icomoon.woff

icomoon.woff

327 ms

font

font

25 ms

recaptcha__en.js

recaptcha__en.js

27 ms

overlay.png

overlay.png

214 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

5 ms

Accessibility Review

kttz.org accessibility score

84

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.

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

kttz.org best practices score

83

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

Browser errors were logged to the console

SEO Factors

kttz.org SEO score

99

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 Kttz.org 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 Kttz.org 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

kttz.org

Open Graph data is detected on the main page of Kttz. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: