Tools & Wizards About Us
wdxe.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

wdxe.com

WDXE - Radio7Media

Page Load Speed

2.1 sec in total

First Response

16 ms

Resources Loaded

1.7 sec

Page Rendered

427 ms

wdxe.com screenshot

About Website

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

Top News Stories insert_link Community Events 10th Annual Abigail’s Bulls and Barrels Event todayJuly 22, 2024 6 insert_link Radio7Media - WLX, WWLX, WDXE State Rep Kip Capley Encourages Local Residen...

Visit wdxe.com

Key Findings

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

Performance Metrics

wdxe.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

0/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value2,520 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

wdxe.com

16 ms

radio7media.com

92 ms

www.radio7media.com

112 ms

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

106 ms

layout.5bce7eb56c23d79d6ab89ab093c281ea.css

120 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wdxe.com, 47% (40 requests) were made to Bloximages.newyork1.vip.townnews.com and 9% (8 requests) were made to Radio7media.com. The less responsive or slowest element that took the longest time to load (391 ms) relates to the external source Polyfill.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 362.0 kB (32%)

Content Size

1.1 MB

After Optimization

757.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wdxe.com main page is 1.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 538.0 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 214.9 kB

  • Original 247.8 kB
  • After minification 217.6 kB
  • After compression 33.0 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. This page needs HTML code to be minified as it can gain 30.2 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 214.9 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 567 B

  • Original 268.0 kB
  • After minification 267.5 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. WDXE images are well optimized though.

JavaScript Optimization

-25%

Potential reduce by 133.8 kB

  • Original 538.0 kB
  • After minification 537.6 kB
  • After compression 404.2 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 133.8 kB or 25% of the original size.

CSS Optimization

-19%

Potential reduce by 12.8 kB

  • Original 66.1 kB
  • After minification 66.1 kB
  • After compression 53.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. Wdxe.com needs all CSS files to be minified and compressed as it can save up to 12.8 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (61%)

Requests Now

75

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wdxe.com

wdxe.com

16 ms

radio7media.com

radio7media.com

92 ms

www.radio7media.com

www.radio7media.com

112 ms

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

106 ms

layout.5bce7eb56c23d79d6ab89ab093c281ea.css

layout.5bce7eb56c23d79d6ab89ab093c281ea.css

120 ms

theme-basic.a7351649a9c39f0af7c6d288a87ef140.css

theme-basic.a7351649a9c39f0af7c6d288a87ef140.css

114 ms

css

css

78 ms

flex-weather-expandable.29365b27620977c8d65433d576ef0ca5.css

flex-weather-expandable.29365b27620977c8d65433d576ef0ca5.css

117 ms

access.d7adebba498598b0ec2c.js

access.d7adebba498598b0ec2c.js

11 ms

jquery.min.d6d18fcf88750a16d256e72626e676a6.js

jquery.min.d6d18fcf88750a16d256e72626e676a6.js

116 ms

user.js

user.js

33 ms

bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js

bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js

116 ms

common.08a61544f369cc43bf02e71b2d10d49f.js

common.08a61544f369cc43bf02e71b2d10d49f.js

146 ms

tnt.ee95c0b6f1daceb31bf5ef84353968c6.js

tnt.ee95c0b6f1daceb31bf5ef84353968c6.js

147 ms

application.3c64d611e594b45dd35b935162e79d85.js

application.3c64d611e594b45dd35b935162e79d85.js

149 ms

polyfill.min.js

polyfill.min.js

391 ms

user-controls.578df3df79d812af55ab13bae47f9857.js

user-controls.578df3df79d812af55ab13bae47f9857.js

147 ms

tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js

tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js

149 ms

op.js

op.js

89 ms

gpt.js

gpt.js

153 ms

tnt.ads.init.c2b9574823d0d16ffc6f20eef83f4232.js

tnt.ads.init.c2b9574823d0d16ffc6f20eef83f4232.js

146 ms

tnt.ads.load.462138bd56c8889eca1bfd14028a582d.js

tnt.ads.load.462138bd56c8889eca1bfd14028a582d.js

148 ms

tracking.js

tracking.js

71 ms

admanager.js

admanager.js

86 ms

impressions.js

impressions.js

148 ms

traffic.js

traffic.js

149 ms

settings.js

settings.js

149 ms

tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js

tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js

147 ms

fontawesome.568f3d1ab17b33ce05854081baadadac.js

fontawesome.568f3d1ab17b33ce05854081baadadac.js

150 ms

tracker.js

tracker.js

83 ms

tnt.ads.core.ee10a41bfea60001b9edb7ab35e5c9e1.js

tnt.ads.core.ee10a41bfea60001b9edb7ab35e5c9e1.js

147 ms

gtm.js

gtm.js

47 ms

analytics.js

analytics.js

18 ms

gtm.js

gtm.js

23 ms

gtm.js

gtm.js

42 ms

publisher:getClientId

publisher:getClientId

102 ms

destination

destination

121 ms

collect

collect

194 ms

collect

collect

334 ms

apstag.js

apstag.js

148 ms

cb1668ce-1ae3-11ec-8535-bfa39475a385.png

cb1668ce-1ae3-11ec-8535-bfa39475a385.png

140 ms

5f4e6af8-216c-11ec-8535-1fabb74fbd37.png

5f4e6af8-216c-11ec-8535-1fabb74fbd37.png

138 ms

63c65a78-216c-11ec-8535-c3edda281299.png

63c65a78-216c-11ec-8535-c3edda281299.png

138 ms

c9cd02f8-3d13-11ee-9872-fbbc0f2e5158.png

c9cd02f8-3d13-11ee-9872-fbbc0f2e5158.png

139 ms

6d56d2f2-216c-11ec-8535-93fe10b15cb8.png

6d56d2f2-216c-11ec-8535-93fe10b15cb8.png

138 ms

4c5d9760-1b14-11ec-8535-7b9bf979056a.png

4c5d9760-1b14-11ec-8535-7b9bf979056a.png

139 ms

c8b3f9d4-1b1a-11ec-8535-9f281b389367.png

c8b3f9d4-1b1a-11ec-8535-9f281b389367.png

148 ms

d5da2a84-1b1a-11ec-8535-074928c61b44.png

d5da2a84-1b1a-11ec-8535-074928c61b44.png

147 ms

df0794d4-1b1a-11ec-8535-430deff1db01.png

df0794d4-1b1a-11ec-8535-430deff1db01.png

146 ms

e6f33734-1b1a-11ec-8535-6376c790c8ef.png

e6f33734-1b1a-11ec-8535-6376c790c8ef.png

147 ms

65b40e85ad011.image.jpg

65b40e85ad011.image.jpg

146 ms

66479fa5b9a3d.image.jpg

66479fa5b9a3d.image.jpg

147 ms

61718ed03ad66.image.png

61718ed03ad66.image.png

279 ms

617304bbe9a41.image.png

617304bbe9a41.image.png

279 ms

6646542744129.image.png

6646542744129.image.png

277 ms

6170d22446ea1.image.jpg

6170d22446ea1.image.jpg

278 ms

65fd33ed29090.image.jpg

65fd33ed29090.image.jpg

278 ms

660d17866b08b.image.jpg

660d17866b08b.image.jpg

278 ms

664859048b1a6.image.jpg

664859048b1a6.image.jpg

322 ms

77985c7e-1b20-11ec-8535-534026a0edae.png

77985c7e-1b20-11ec-8535-534026a0edae.png

323 ms

pubads_impl.js

pubads_impl.js

106 ms

tracker.gif

tracker.gif

101 ms

apstag.js

apstag.js

232 ms

va9E4kDNxMZdWfMOD5Vvl4jO.ttf

va9E4kDNxMZdWfMOD5Vvl4jO.ttf

230 ms

va9B4kDNxMZdWfMOD5VnPKreRhf_.ttf

va9B4kDNxMZdWfMOD5VnPKreRhf_.ttf

293 ms

va9B4kDNxMZdWfMOD5VnSKzeRhf_.ttf

va9B4kDNxMZdWfMOD5VnSKzeRhf_.ttf

334 ms

va9B4kDNxMZdWfMOD5VnLK3eRhf_.ttf

va9B4kDNxMZdWfMOD5VnLK3eRhf_.ttf

339 ms

analytics.min.js

analytics.min.js

229 ms

132916964

132916964

264 ms

b63feadc-1ae9-11ec-8535-e345a778ecfc.jpg

b63feadc-1ae9-11ec-8535-e345a778ecfc.jpg

93 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoUoOmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoUoOmb2Rm.ttf

104 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf

106 ms

settings

settings

40 ms

classichitswlx.com

classichitswlx.com

365 ms

AGSKWxVhQO2ptvMa-ip3jORfdVNYE3dJ3UCBIh_v0VPgLeEDERt-xnmRcfmbWwDpoHzBIPhhYI6nSXn5iwGlx5S6BBMluPQe8UXwjMgulJV-8G8BbgdpL-7nDihp5Mn-NUupVZ_e1mUHiQ==

AGSKWxVhQO2ptvMa-ip3jORfdVNYE3dJ3UCBIh_v0VPgLeEDERt-xnmRcfmbWwDpoHzBIPhhYI6nSXn5iwGlx5S6BBMluPQe8UXwjMgulJV-8G8BbgdpL-7nDihp5Mn-NUupVZ_e1mUHiQ==

83 ms

uid2SecureSignal.js

uid2SecureSignal.js

171 ms

esp.js

esp.js

184 ms

publishertag.ids.js

publishertag.ids.js

157 ms

esp.js

esp.js

169 ms

encrypted-tag-g.js

encrypted-tag-g.js

272 ms

sync.min.js

sync.min.js

160 ms

pubcid.min.js

pubcid.min.js

179 ms

ob.js

ob.js

180 ms

870.bundle.6e2976b75e60ab2b2bf8.js

870.bundle.6e2976b75e60ab2b2bf8.js

80 ms

tsub-middleware.bundle.77315eced46c5ae4c052.js

tsub-middleware.bundle.77315eced46c5ae4c052.js

130 ms

map

map

83 ms

Accessibility Review

wdxe.com accessibility score

96

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.

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

wdxe.com 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

wdxe.com SEO score

83

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

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

wdxe.com

Open Graph description is not detected on the main page of WDXE. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: