Tools & Wizards About Us
1031iheartaustin.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

1031iheartaustin.com

103.1 Austin's 80s Station - 80s Hits & Your Home For The Sandy Show

Page Load Speed

6 sec in total

First Response

2.6 sec

Resources Loaded

3.3 sec

Page Rendered

131 ms

1031iheartaustin.com screenshot

About Website

Click here to check amazing 103 1iheart Austin content. Otherwise, check out these important facts you probably never knew about 1031iheartaustin.com

103.1 is Austin, Texas' home 80s hits and The Sandy Show. Broadcasting on KVET-HD2 at 103.1 FM and anywhere on iHeartRadio.

Visit 1031iheartaustin.com

Key Findings

We analyzed 1031iheartaustin.com page load time and found that the first response time was 2.6 sec and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

1031iheartaustin.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

49/100

25%

SI (Speed Index)

Value14.6 s

1/100

10%

TBT (Total Blocking Time)

Value7,020 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.452

20/100

15%

TTI (Time to Interactive)

Value30.5 s

0/100

10%

Network Requests Diagram

1031austin.iheart.com

2605 ms

bundle.b4784393326cfefc06fa.css

207 ms

sites-local.f4601bc8219098567a86.css

235 ms

core-components-tiles-OnairTileLoader-component.d9b89684bedbb0c4b00f.css

243 ms

core-page-blocks-datasource-DatasourceLoader-component.d0d7c906ff67d191c4e4.css

266 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original 1031iheartaustin.com, 7% (3 requests) were made to I.iheart.com and 2% (1 request) were made to 1031austin.iheart.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source 1031austin.iheart.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 662.1 kB (74%)

Content Size

892.2 kB

After Optimization

230.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 1031iheartaustin.com main page is 892.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. 70% of websites need less resources to load. HTML takes 591.2 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 481.0 kB

  • Original 591.2 kB
  • After minification 590.8 kB
  • After compression 110.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 481.0 kB or 81% of the original size.

Image Optimization

-8%

Potential reduce by 546 B

  • Original 7.2 kB
  • After minification 6.6 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. 103 1iheart Austin images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 177.7 kB

  • Original 269.6 kB
  • After minification 269.6 kB
  • After compression 91.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 177.7 kB or 66% of the original size.

CSS Optimization

-12%

Potential reduce by 2.9 kB

  • Original 24.3 kB
  • After minification 24.1 kB
  • After compression 21.4 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. 1031iheartaustin.com needs all CSS files to be minified and compressed as it can save up to 2.9 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (88%)

Requests Now

41

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

1031austin.iheart.com

1031austin.iheart.com

2605 ms

bundle.b4784393326cfefc06fa.css

bundle.b4784393326cfefc06fa.css

207 ms

sites-local.f4601bc8219098567a86.css

sites-local.f4601bc8219098567a86.css

235 ms

core-components-tiles-OnairTileLoader-component.d9b89684bedbb0c4b00f.css

core-components-tiles-OnairTileLoader-component.d9b89684bedbb0c4b00f.css

243 ms

core-page-blocks-datasource-DatasourceLoader-component.d0d7c906ff67d191c4e4.css

core-page-blocks-datasource-DatasourceLoader-component.d0d7c906ff67d191c4e4.css

266 ms

Datasource-component.21b2d627bf3f26b77cdb.css

Datasource-component.21b2d627bf3f26b77cdb.css

240 ms

Grid-component.9e05f3f8fa0e6b993347.css

Grid-component.9e05f3f8fa0e6b993347.css

240 ms

components-tiles-ContentTile-component.a5e9ee6f3bc07a62d945.css

components-tiles-ContentTile-component.a5e9ee6f3bc07a62d945.css

259 ms

core-page-blocks-music-MusicTile-component.c0f2337b7d57cb7e8b6d.css

core-page-blocks-music-MusicTile-component.c0f2337b7d57cb7e8b6d.css

262 ms

Heading-component.d79a5c95e6ef67a97bca.css

Heading-component.d79a5c95e6ef67a97bca.css

258 ms

LoadMoreFromCursor-component.4a7a0f66bc2d890b3034.css

LoadMoreFromCursor-component.4a7a0f66bc2d890b3034.css

255 ms

core-page-blocks-datasource-DatasourceTileLoader-component.21b2d627bf3f26b77cdb.css

core-page-blocks-datasource-DatasourceTileLoader-component.21b2d627bf3f26b77cdb.css

247 ms

FauxButton-component.1f25bb623660eb4f88c1.css

FauxButton-component.1f25bb623660eb4f88c1.css

259 ms

Eyebrow-component.5399b326d85b58042faf.css

Eyebrow-component.5399b326d85b58042faf.css

262 ms

AptivadaKeywordContest-component.ff94331856c0bb091379.css

AptivadaKeywordContest-component.ff94331856c0bb091379.css

258 ms

moatheader.js

moatheader.js

498 ms

612e4a1b7010a28552d546a7

612e4a1b7010a28552d546a7

245 ms

runtime.6b4924f16f0540cb95f3.js

runtime.6b4924f16f0540cb95f3.js

396 ms

vendor.710290aee3274352d59a.js

vendor.710290aee3274352d59a.js

428 ms

bundle.493e54a605c4909893ed.js

bundle.493e54a605c4909893ed.js

459 ms

src_app_core_chrome_AppTray_component_tsx-src_app_core_chrome_Footer_component_tsx-src_app_co-d67451.a19849dbbcd5f0a50bfc.js

src_app_core_chrome_AppTray_component_tsx-src_app_core_chrome_Footer_component_tsx-src_app_co-d67451.a19849dbbcd5f0a50bfc.js

390 ms

sites-local.37d46712c4175db4e3c9.js

sites-local.37d46712c4175db4e3c9.js

388 ms

MagicLink-component.d8ebec3fff267f1ceb57.js

MagicLink-component.d8ebec3fff267f1ceb57.js

336 ms

core-components-tiles-OnairTileLoader-component.3660133e9ae8cc8c3dbd.js

core-components-tiles-OnairTileLoader-component.3660133e9ae8cc8c3dbd.js

372 ms

core-page-blocks-datasource-DatasourceLoader-component.c4fb328c3b6211b7ca76.js

core-page-blocks-datasource-DatasourceLoader-component.c4fb328c3b6211b7ca76.js

374 ms

Datasource-component.1c017bbd80cc11bfd075.js

Datasource-component.1c017bbd80cc11bfd075.js

377 ms

Grid-component.d1391a391db391ba3293.js

Grid-component.d1391a391db391ba3293.js

382 ms

ContentFeedItem-component.18a0bca380789d53b358.js

ContentFeedItem-component.18a0bca380789d53b358.js

382 ms

LeadFeedItem-component.7349c61d3b98434fc28f.js

LeadFeedItem-component.7349c61d3b98434fc28f.js

381 ms

components-tiles-ContentTile-component.c15ed61ef8b431c7c7ce.js

components-tiles-ContentTile-component.c15ed61ef8b431c7c7ce.js

381 ms

core-page-blocks-music-MusicTile-component.bb537e64018c66baf29c.js

core-page-blocks-music-MusicTile-component.bb537e64018c66baf29c.js

381 ms

core-page-blocks-podcast-PodcastsLoader-component.e465f719fda6f62933b2.js

core-page-blocks-podcast-PodcastsLoader-component.e465f719fda6f62933b2.js

387 ms

Heading-component.28a08a32215f3defa880.js

Heading-component.28a08a32215f3defa880.js

386 ms

LoadMoreFromCursor-component.a8dbeb4c1b1e9069f823.js

LoadMoreFromCursor-component.a8dbeb4c1b1e9069f823.js

378 ms

core-page-blocks-datasource-DatasourceTileLoader-component.59cc1549bce6b4b5800c.js

core-page-blocks-datasource-DatasourceTileLoader-component.59cc1549bce6b4b5800c.js

378 ms

FauxButton-component.7c8a6b13cd1c228006f2.js

FauxButton-component.7c8a6b13cd1c228006f2.js

377 ms

core-page-blocks-contest-KeywordContestLoader-component.5435e7b603530e153d88.js

core-page-blocks-contest-KeywordContestLoader-component.5435e7b603530e153d88.js

383 ms

Eyebrow-component.bb3cb3f916a8f984fa1c.js

Eyebrow-component.bb3cb3f916a8f984fa1c.js

381 ms

DateTimeDisplay-component.9a93eb94463384ae2d8e.js

DateTimeDisplay-component.9a93eb94463384ae2d8e.js

382 ms

f79fc341-a979-4863-81b0-eea1ddc6e07b

f79fc341-a979-4863-81b0-eea1ddc6e07b

317 ms

f79fc341-a979-4863-81b0-eea1ddc6e07b

f79fc341-a979-4863-81b0-eea1ddc6e07b

320 ms

AptivadaKeywordContest-component.d68029097edc45b79723.js

AptivadaKeywordContest-component.d68029097edc45b79723.js

311 ms

Accessibility Review

1031iheartaustin.com accessibility score

100

Accessibility Issues

Best Practices

1031iheartaustin.com 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

High

Page has valid source maps

SEO Factors

1031iheartaustin.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 1031iheartaustin.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 1031iheartaustin.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

1031iheartaustin.com

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