Tools & Wizards About Us
wilm.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

wilm.com

News Radio 1450 WILM - Wilmington's News, Traffic & Weather

Page Load Speed

1.3 sec in total

First Response

494 ms

Resources Loaded

768 ms

Page Rendered

56 ms

wilm.com screenshot

About Website

Welcome to wilm.com homepage info - get ready to check WILM best content right away, or after learning these important things about wilm.com

A conservative news talk station based out of Wilmington, Delaware featuring Mike Opelka, Rush Limbaugh, Sean Hannity, and Glenn Beck.

Visit wilm.com

Key Findings

We analyzed Wilm.com page load time and found that the first response time was 494 ms and then it took 824 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

wilm.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value2,970 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value14.5 s

9/100

10%

Network Requests Diagram

wilm.iheart.com

494 ms

bundle.cd0526b54749d3acd9a0.css

58 ms

local.bc06f128f534d4a5d747.css

57 ms

core-components-tiles-OnairTileLoader-component.12f62d6d6ad5771d626e.css

64 ms

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

62 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Wilm.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 (494 ms) relates to the external source Wilm.iheart.com.

Page Optimization Overview & Recommendations

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

Content Size

2.2 MB

After Optimization

936.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 1.1 MB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 256.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 1.1 MB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 151 B

  • Original 76.4 kB
  • After minification 76.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. WILM images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 181.6 kB

  • Original 757.0 kB
  • After minification 757.0 kB
  • After compression 575.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 181.6 kB or 24% of the original size.

CSS Optimization

-5%

Potential reduce by 1.4 kB

  • Original 29.8 kB
  • After minification 29.7 kB
  • After compression 28.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. Wilm.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

59

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wilm.iheart.com

wilm.iheart.com

494 ms

bundle.cd0526b54749d3acd9a0.css

bundle.cd0526b54749d3acd9a0.css

58 ms

local.bc06f128f534d4a5d747.css

local.bc06f128f534d4a5d747.css

57 ms

core-components-tiles-OnairTileLoader-component.12f62d6d6ad5771d626e.css

core-components-tiles-OnairTileLoader-component.12f62d6d6ad5771d626e.css

64 ms

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

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

62 ms

Datasource-component.a1eb25fbdc158e499608.css

Datasource-component.a1eb25fbdc158e499608.css

62 ms

Grid-component.9e05f3f8fa0e6b993347.css

Grid-component.9e05f3f8fa0e6b993347.css

63 ms

components-tiles-ContentTile-component.a5e9ee6f3bc07a62d945.css

components-tiles-ContentTile-component.a5e9ee6f3bc07a62d945.css

64 ms

TrafficTile-component.79b6ef8f3442074e2437.css

TrafficTile-component.79b6ef8f3442074e2437.css

64 ms

Heading-component.d79a5c95e6ef67a97bca.css

Heading-component.d79a5c95e6ef67a97bca.css

67 ms

LoadMoreFromCursor-component.4a7a0f66bc2d890b3034.css

LoadMoreFromCursor-component.4a7a0f66bc2d890b3034.css

74 ms

Show-component.608ec1ff0656c8b676a1.css

Show-component.608ec1ff0656c8b676a1.css

65 ms

core-page-blocks-datasource-DatasourceTileLoader-component.a1eb25fbdc158e499608.css

core-page-blocks-datasource-DatasourceTileLoader-component.a1eb25fbdc158e499608.css

64 ms

FauxButton-component.1f25bb623660eb4f88c1.css

FauxButton-component.1f25bb623660eb4f88c1.css

66 ms

Eyebrow-component.23e83d8b8cab22ea99d6.css

Eyebrow-component.23e83d8b8cab22ea99d6.css

67 ms

AptivadaKeywordContest-component.a21f13419d9d48bf409a.css

AptivadaKeywordContest-component.a21f13419d9d48bf409a.css

68 ms

Podcasts-component.570accd833088f4c4e7d.css

Podcasts-component.570accd833088f4c4e7d.css

67 ms

ImageTile-component.c2cbd469fbc0bd11cbdf.css

ImageTile-component.c2cbd469fbc0bd11cbdf.css

69 ms

Card-component.c66d212af09897afcdd6.css

Card-component.c66d212af09897afcdd6.css

69 ms

WeatherTile-component.ca557d80a0c5075ed0c1.css

WeatherTile-component.ca557d80a0c5075ed0c1.css

74 ms

sdk.js

sdk.js

195 ms

moatheader.js

moatheader.js

143 ms

ebx.js

ebx.js

71 ms

runtime.81b1e67b144d762b24f2.js

runtime.81b1e67b144d762b24f2.js

61 ms

vendor.e92bdd3e5e6961dec2e3.js

vendor.e92bdd3e5e6961dec2e3.js

124 ms

bundle.e5dc8b716203227c4c9e.js

bundle.e5dc8b716203227c4c9e.js

128 ms

packages-renderer-shared-ui-src-elements-MagicLink-component.e03d349031c3952372e8.js

packages-renderer-shared-ui-src-elements-MagicLink-component.e03d349031c3952372e8.js

60 ms

src_app_core_chrome_AppTray_component_tsx-src_app_core_chrome_HeaderSearch_component_tsx-src_-b801d3.6041e11b8d0e121e52b7.js

src_app_core_chrome_AppTray_component_tsx-src_app_core_chrome_HeaderSearch_component_tsx-src_-b801d3.6041e11b8d0e121e52b7.js

126 ms

local.886e64ad0766cf5f72a5.js

local.886e64ad0766cf5f72a5.js

125 ms

core-components-tiles-OnairTileLoader-component.22fd96ce3a97461201e5.js

core-components-tiles-OnairTileLoader-component.22fd96ce3a97461201e5.js

125 ms

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

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

125 ms

packages_renderer_shared_core_src_lib_ads_ts.a0e79586bbded4410f92.js

packages_renderer_shared_core_src_lib_ads_ts.a0e79586bbded4410f92.js

125 ms

Datasource-component.1423c7d635806130822c.js

Datasource-component.1423c7d635806130822c.js

128 ms

Grid-component.48dae21730bceb9ee5e7.js

Grid-component.48dae21730bceb9ee5e7.js

126 ms

ContentFeedItem-component.a58f9b17ed1802cd6512.js

ContentFeedItem-component.a58f9b17ed1802cd6512.js

129 ms

components-tiles-ContentTile-component.8fe9a91f6ecd8ec889d2.js

components-tiles-ContentTile-component.8fe9a91f6ecd8ec889d2.js

129 ms

LeadFeedItem-component.f9b025ed7a795a039e16.js

LeadFeedItem-component.f9b025ed7a795a039e16.js

129 ms

core-components-tiles-WeatherTileLoader-component.224b5c1493848aa4f0f6.js

core-components-tiles-WeatherTileLoader-component.224b5c1493848aa4f0f6.js

128 ms

TrafficTile-component.47ac314dfe91b6ebc04f.js

TrafficTile-component.47ac314dfe91b6ebc04f.js

129 ms

Heading-component.ea88c81b8d34c977158c.js

Heading-component.ea88c81b8d34c977158c.js

134 ms

LoadMoreFromCursor-component.bb890d9dab9374f42e37.js

LoadMoreFromCursor-component.bb890d9dab9374f42e37.js

89 ms

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

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

90 ms

ShowCollection-component.9692637de0ea45061f03.js

ShowCollection-component.9692637de0ea45061f03.js

89 ms

Show-component.7f0dafb91f97b90e8cff.js

Show-component.7f0dafb91f97b90e8cff.js

89 ms

core-page-blocks-datasource-DatasourceTileLoader-component.05d77890dc9884cc76e2.js

core-page-blocks-datasource-DatasourceTileLoader-component.05d77890dc9884cc76e2.js

85 ms

FauxButton-component.6f17f4f82d52801c5c49.js

FauxButton-component.6f17f4f82d52801c5c49.js

88 ms

core-page-blocks-contest-KeywordContestLoader-component.5e0cc4120d526a5ea860.js

core-page-blocks-contest-KeywordContestLoader-component.5e0cc4120d526a5ea860.js

86 ms

Eyebrow-component.533482f1ba2c4fcd4202.js

Eyebrow-component.533482f1ba2c4fcd4202.js

85 ms

AptivadaKeywordContest-component.d932ebf2afeb78ef5324.js

AptivadaKeywordContest-component.d932ebf2afeb78ef5324.js

133 ms

vendors-node_modules_pnpm_isomorphic-dompurify_0_27_0_node_modules_isomorphic-dompurify_browser_js.05cdd4f29edec5e3d7e3.js

vendors-node_modules_pnpm_isomorphic-dompurify_0_27_0_node_modules_isomorphic-dompurify_browser_js.05cdd4f29edec5e3d7e3.js

132 ms

Podcasts-component.ab2989f0ebc0ae9ef4c1.js

Podcasts-component.ab2989f0ebc0ae9ef4c1.js

131 ms

ImageTile-component.b3ff14a77346457b64fe.js

ImageTile-component.b3ff14a77346457b64fe.js

130 ms

Card-component.24dee8840408569eb2c3.js

Card-component.24dee8840408569eb2c3.js

130 ms

WeatherTile-component.e8eb1af90b1d00d39f16.js

WeatherTile-component.e8eb1af90b1d00d39f16.js

129 ms

60ccbaf51b3a402cbd502641

60ccbaf51b3a402cbd502641

156 ms

f79fc341-a979-4863-81b0-eea1ddc6e07b

f79fc341-a979-4863-81b0-eea1ddc6e07b

84 ms

627ed0263f19c6325b37ec16

627ed0263f19c6325b37ec16

86 ms

v2

v2

54 ms

n.js

n.js

41 ms

iframe.html

iframe.html

8 ms

Accessibility Review

wilm.com accessibility score

97

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

Best Practices

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

wilm.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 Wilm.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 Wilm.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

wilm.com

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