Tools & Wizards About Us
wtkg.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

wtkg.com

WTKG 1230 AM - Grand Rapids' Choice for Talk Radio

Page Load Speed

4.8 sec in total

First Response

2.1 sec

Resources Loaded

2.5 sec

Page Rendered

58 ms

wtkg.com screenshot

About Website

Click here to check amazing WTKG content for United States. Otherwise, check out these important facts you probably never knew about wtkg.com

TALK 1230 WTKG

Visit wtkg.com

Key Findings

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

Performance Metrics

wtkg.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

21/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value3,200 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

wtkg.iheart.com

2148 ms

bundle.4703be0156eafd97692e.css

46 ms

local.7d59bc1bb8dc1449c06f.css

53 ms

core-components-tiles-OnairTileLoader-component.2a50ea6cc4121789b246.css

55 ms

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

57 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Wtkg.com, 5% (3 requests) were made to I.iheart.com and 3% (2 requests) were made to Z.moatads.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Wtkg.iheart.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (57%)

Content Size

1.8 MB

After Optimization

791.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 849.0 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 209.3 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 849.0 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 38.2 kB
  • After minification 38.2 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. WTKG images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 193.1 kB

  • Original 708.9 kB
  • After minification 708.9 kB
  • After compression 515.8 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 193.1 kB or 27% of the original size.

CSS Optimization

-5%

Potential reduce by 1.4 kB

  • Original 29.5 kB
  • After minification 29.4 kB
  • After compression 28.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. Wtkg.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 48 (86%)

Requests Now

56

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wtkg.iheart.com

wtkg.iheart.com

2148 ms

bundle.4703be0156eafd97692e.css

bundle.4703be0156eafd97692e.css

46 ms

local.7d59bc1bb8dc1449c06f.css

local.7d59bc1bb8dc1449c06f.css

53 ms

core-components-tiles-OnairTileLoader-component.2a50ea6cc4121789b246.css

core-components-tiles-OnairTileLoader-component.2a50ea6cc4121789b246.css

55 ms

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

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

57 ms

Datasource-component.82db539a757e1359e8df.css

Datasource-component.82db539a757e1359e8df.css

57 ms

Grid-component.9e05f3f8fa0e6b993347.css

Grid-component.9e05f3f8fa0e6b993347.css

56 ms

components-tiles-ContentTile-component.a5e9ee6f3bc07a62d945.css

components-tiles-ContentTile-component.a5e9ee6f3bc07a62d945.css

56 ms

TrafficTile-component.cff947779ea3a28b204a.css

TrafficTile-component.cff947779ea3a28b204a.css

63 ms

Heading-component.d79a5c95e6ef67a97bca.css

Heading-component.d79a5c95e6ef67a97bca.css

62 ms

LoadMoreFromCursor-component.4a7a0f66bc2d890b3034.css

LoadMoreFromCursor-component.4a7a0f66bc2d890b3034.css

62 ms

Show-component.608ec1ff0656c8b676a1.css

Show-component.608ec1ff0656c8b676a1.css

61 ms

core-page-blocks-datasource-DatasourceTileLoader-component.82db539a757e1359e8df.css

core-page-blocks-datasource-DatasourceTileLoader-component.82db539a757e1359e8df.css

61 ms

WeatherTile-component.ca557d80a0c5075ed0c1.css

WeatherTile-component.ca557d80a0c5075ed0c1.css

61 ms

Podcasts-component.2ac6c6287428cf01e9b9.css

Podcasts-component.2ac6c6287428cf01e9b9.css

64 ms

FauxButton-component.1f25bb623660eb4f88c1.css

FauxButton-component.1f25bb623660eb4f88c1.css

67 ms

ImageTile-component.c2cbd469fbc0bd11cbdf.css

ImageTile-component.c2cbd469fbc0bd11cbdf.css

67 ms

Card-component.c66d212af09897afcdd6.css

Card-component.c66d212af09897afcdd6.css

65 ms

AptivadaKeywordContest-component.a21f13419d9d48bf409a.css

AptivadaKeywordContest-component.a21f13419d9d48bf409a.css

66 ms

moatheader.js

moatheader.js

60 ms

ebx.js

ebx.js

156 ms

runtime.5b82aa01021d7e67709b.js

runtime.5b82aa01021d7e67709b.js

53 ms

vendor.062490e9574784ceecdc.js

vendor.062490e9574784ceecdc.js

137 ms

bundle.eee3b026d88b2142ed93.js

bundle.eee3b026d88b2142ed93.js

150 ms

packages-renderer-shared-ui-src-elements-MagicLink-component.37e7dfeb021ef49d9f6f.js

packages-renderer-shared-ui-src-elements-MagicLink-component.37e7dfeb021ef49d9f6f.js

135 ms

src_app_core_chrome_AppTray_component_tsx-src_app_core_chrome_HeaderSearch_component_tsx-src_-b801d3.ebb7c95d698279b1c9ec.js

src_app_core_chrome_AppTray_component_tsx-src_app_core_chrome_HeaderSearch_component_tsx-src_-b801d3.ebb7c95d698279b1c9ec.js

136 ms

local.a5b480bb028a49b07c6c.js

local.a5b480bb028a49b07c6c.js

137 ms

core-components-tiles-OnairTileLoader-component.3c9c776801ce3f5ccf05.js

core-components-tiles-OnairTileLoader-component.3c9c776801ce3f5ccf05.js

134 ms

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

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

136 ms

packages_renderer_shared_core_src_lib_ads_ts.1c411bb05fe7a8d6fb44.js

packages_renderer_shared_core_src_lib_ads_ts.1c411bb05fe7a8d6fb44.js

137 ms

Datasource-component.09c541938624ea67842c.js

Datasource-component.09c541938624ea67842c.js

139 ms

Grid-component.48dae21730bceb9ee5e7.js

Grid-component.48dae21730bceb9ee5e7.js

138 ms

ContentFeedItem-component.2c07f0e7be984e8aee02.js

ContentFeedItem-component.2c07f0e7be984e8aee02.js

140 ms

components-tiles-ContentTile-component.22ddd6a7b1c8a1bc4e2d.js

components-tiles-ContentTile-component.22ddd6a7b1c8a1bc4e2d.js

137 ms

LeadFeedItem-component.4330af319e52f7557387.js

LeadFeedItem-component.4330af319e52f7557387.js

138 ms

core-components-tiles-WeatherTileLoader-component.3076f6660778382f42b1.js

core-components-tiles-WeatherTileLoader-component.3076f6660778382f42b1.js

139 ms

TrafficTile-component.01dffae824fc382d134e.js

TrafficTile-component.01dffae824fc382d134e.js

141 ms

Heading-component.ea88c81b8d34c977158c.js

Heading-component.ea88c81b8d34c977158c.js

140 ms

LoadMoreFromCursor-component.dd840a1844d3d6bb0d7d.js

LoadMoreFromCursor-component.dd840a1844d3d6bb0d7d.js

140 ms

core-page-blocks-podcast-PodcastsLoader-component.71edb632222c77f48f93.js

core-page-blocks-podcast-PodcastsLoader-component.71edb632222c77f48f93.js

109 ms

ShowCollection-component.0c3f9b3068fe83748412.js

ShowCollection-component.0c3f9b3068fe83748412.js

107 ms

Show-component.cdfd0315af774eaef8dd.js

Show-component.cdfd0315af774eaef8dd.js

105 ms

core-page-blocks-datasource-DatasourceTileLoader-component.70fbc1958e35a8aed3b5.js

core-page-blocks-datasource-DatasourceTileLoader-component.70fbc1958e35a8aed3b5.js

105 ms

core-page-blocks-contest-KeywordContestLoader-component.eb063dc982e7b1285f9b.js

core-page-blocks-contest-KeywordContestLoader-component.eb063dc982e7b1285f9b.js

104 ms

WeatherTile-component.e8e44d3a690efdf646b4.js

WeatherTile-component.e8e44d3a690efdf646b4.js

103 ms

vendors-node_modules_pnpm_isomorphic-dompurify_0_23_0_node_modules_isomorphic-dompurify_browser_js.132aa67d79fbc3864c41.js

vendors-node_modules_pnpm_isomorphic-dompurify_0_23_0_node_modules_isomorphic-dompurify_browser_js.132aa67d79fbc3864c41.js

106 ms

Podcasts-component.c822825f35d41178cdf7.js

Podcasts-component.c822825f35d41178cdf7.js

102 ms

FauxButton-component.6f17f4f82d52801c5c49.js

FauxButton-component.6f17f4f82d52801c5c49.js

101 ms

ImageTile-component.b3ff14a77346457b64fe.js

ImageTile-component.b3ff14a77346457b64fe.js

102 ms

Card-component.24dee8840408569eb2c3.js

Card-component.24dee8840408569eb2c3.js

101 ms

AptivadaKeywordContest-component.b7ea73f8063fca6968f6.js

AptivadaKeywordContest-component.b7ea73f8063fca6968f6.js

102 ms

360057661571

360057661571

137 ms

641b3902de66c5274866b3c6

641b3902de66c5274866b3c6

310 ms

f79fc341-a979-4863-81b0-eea1ddc6e07b

f79fc341-a979-4863-81b0-eea1ddc6e07b

83 ms

627ed0263f19c6325b37ec16

627ed0263f19c6325b37ec16

83 ms

v2

v2

66 ms

n.js

n.js

54 ms

iframe.html

iframe.html

13 ms

Accessibility Review

wtkg.com accessibility score

100

Accessibility Issues

Best Practices

wtkg.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

wtkg.com SEO score

93

Search Engine Optimization Advices

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

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 Wtkg.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 Wtkg.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

wtkg.com

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