Tools & Wizards About Us
wis.community screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

wis.community

Eye on Dunn County | Community News from Dunn County, WI

Page Load Speed

2.3 sec in total

First Response

242 ms

Resources Loaded

1.6 sec

Page Rendered

444 ms

wis.community screenshot

About Website

Click here to check amazing WI S content. Otherwise, check out these important facts you probably never knew about wis.community

Eye On Dunn County is a source of news from Dunn County Wisconsin. We feature local government, environment, schools, and general information. Come to us for Menomonie and Dunn County news.

Visit wis.community

Key Findings

We analyzed Wis.community page load time and found that the first response time was 242 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

wis.community performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value1,920 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.089

92/100

15%

TTI (Time to Interactive)

Value18.1 s

3/100

10%

Network Requests Diagram

wis.community

242 ms

eyeondunn.com

267 ms

matomo.js

33 ms

sdk.js

27 ms

fbevents.js

48 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Wis.community, 34% (11 requests) were made to Eyeondunn.com and 22% (7 requests) were made to Cdnres.willyweather.com. The less responsive or slowest element that took the longest time to load (429 ms) relates to the external source Cdnres.willyweather.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 540.3 kB (41%)

Content Size

1.3 MB

After Optimization

783.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wis.community main page is 1.3 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. Javascripts take 977.9 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 114.8 kB

  • Original 138.0 kB
  • After minification 123.8 kB
  • After compression 23.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 114.8 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 21 B

  • Original 153.9 kB
  • After minification 153.9 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. WI S images are well optimized though.

JavaScript Optimization

-43%

Potential reduce by 425.2 kB

  • Original 977.9 kB
  • After minification 977.9 kB
  • After compression 552.7 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 425.2 kB or 43% of the original size.

CSS Optimization

-0%

Potential reduce by 264 B

  • Original 54.2 kB
  • After minification 54.2 kB
  • After compression 54.0 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. Wis.community has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 20 (71%)

Requests Now

28

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wis.community

wis.community

242 ms

eyeondunn.com

eyeondunn.com

267 ms

matomo.js

matomo.js

33 ms

sdk.js

sdk.js

27 ms

fbevents.js

fbevents.js

48 ms

loadView.html

loadView.html

349 ms

css_okFDq7ejBieJ7q5Yb6GbdOtFdXR8RE_aIHjIpgcL9lA.css

css_okFDq7ejBieJ7q5Yb6GbdOtFdXR8RE_aIHjIpgcL9lA.css

45 ms

all.min.css

all.min.css

45 ms

css_biUGLzt9K8klGobMMHuL6EaeFNImxerZw0LeL6O4npE.css

css_biUGLzt9K8klGobMMHuL6EaeFNImxerZw0LeL6O4npE.css

45 ms

css_IfShtky95p8wkCqewnCmNlgdF_B4aRXj4cBF4mEh7Ws.css

css_IfShtky95p8wkCqewnCmNlgdF_B4aRXj4cBF4mEh7Ws.css

46 ms

modernizr-custom-d8-dxpr-theme.js

modernizr-custom-d8-dxpr-theme.js

45 ms

js_TJd3l_l5Q9hYTUflStBwxagKQA8eOSEjMYO-8Mxk1Pc.js

js_TJd3l_l5Q9hYTUflStBwxagKQA8eOSEjMYO-8Mxk1Pc.js

72 ms

gtag.js

gtag.js

91 ms

js_fkuGjtJsu1055gtHazOfWhJ9rRFI4JFzgmsLNg9YD88.js

js_fkuGjtJsu1055gtHazOfWhJ9rRFI4JFzgmsLNg9YD88.js

74 ms

transparent-logo-small.png

transparent-logo-small.png

72 ms

sdk.js

sdk.js

47 ms

matomo.php

matomo.php

145 ms

js_rFUOm6Hzd-msgC-lhr0acF_laNE71DAe6hlxjBNxcx4.js

js_rFUOm6Hzd-msgC-lhr0acF_laNE71DAe6hlxjBNxcx4.js

51 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

77 ms

92 ms

universal.js

universal.js

139 ms

gpt.js

gpt.js

73 ms

loadView.html

loadView.html

263 ms

fa-brands-400.ttf

fa-brands-400.ttf

31 ms

pubads_impl.js

pubads_impl.js

30 ms

1005060

1005060

70 ms

cssView.1.42.64.html

cssView.1.42.64.html

429 ms

widgetSideBar.1.42.64.js

widgetSideBar.1.42.64.js

156 ms

analytics.js

analytics.js

19 ms

sprite.png

sprite.png

8 ms

ui-loader.gif

ui-loader.gif

6 ms

bgs.jpg

bgs.jpg

6 ms

Accessibility Review

wis.community accessibility score

93

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

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

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

wis.community 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

wis.community SEO score

83

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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 Wis.community 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 Wis.community 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

wis.community

Open Graph description is not detected on the main page of WI S. 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: