3.7 sec in total
72 ms
3 sec
566 ms
Visit evansville.net now to see the best up-to-date Evansville content and also check out these interesting facts you probably never knew about evansville.net
Welcome to Windstream - Your destination for breaking news, entertainment, sports, games, trending videos, weather and much more.
Visit evansville.netWe analyzed Evansville.net page load time and found that the first response time was 72 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
evansville.net performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value17.9 s
0/100
25%
Value24.6 s
0/100
10%
Value10,290 ms
0/100
30%
Value0.631
9/100
15%
Value47.3 s
0/100
10%
72 ms
478 ms
91 ms
123 ms
44 ms
Our browser made a total of 204 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Evansville.net, 9% (19 requests) were made to Static.garnet.synacor.com and 7% (14 requests) were made to S.yimg.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Px.owneriq.net.
Page size can be reduced by 1.8 MB (43%)
4.2 MB
2.4 MB
In fact, the total size of Evansville.net main page is 4.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. 85% 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. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 980.5 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 980.5 kB or 91% of the original size.
Potential reduce by 54.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. Evansville images are well optimized though.
Potential reduce by 803.1 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 803.1 kB or 58% of the original size.
Number of requests can be reduced by 107 (58%)
186
79
The browser has sent 186 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Evansville. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 62 to 1 for JavaScripts and as a result speed up the page load time.
evansville.net
72 ms
www.windstream.net
478 ms
res.php
91 ms
res.php
123 ms
res.php
44 ms
satelliteLib-2ac5be31d865383e58438363c86dd3409ef4ce17.js
8 ms
res.php
44 ms
synacor.js
111 ms
track.gif
56 ms
mbox-contents-9afb00cdd4676c759c023f17fc251ccfcacafe05.js
20 ms
gpt.js
46 ms
synacor.js
153 ms
targets
118 ms
json
89 ms
loader.js
17 ms
client_logo_dark_lg.png
37 ms
client_logo_light_lg.png
37 ms
enhanced_by_google.png
36 ms
adchoices_icon.png
37 ms
sourcesanspro-regular.svgz
69 ms
sourcesanspro-regular.woff
67 ms
pubads_impl_147.js
63 ms
load.js
54 ms
impl.271-68-RELEASE.js
7 ms
beacon.js
46 ms
sourcesanspro-light.svgz
79 ms
sourcesanspro-light.woff
78 ms
container.html
23 ms
pmk-201725013.3.js
19 ms
jpt
34 ms
cygnus
202 ms
jpt
60 ms
jpt
35 ms
jpt
62 ms
jpt
62 ms
jpt
57 ms
gshowad.js
24 ms
publishertag.js
27 ms
;cfp=1;rndc=1504714239;noperf=1;alias=;cmd=bid;cors=yes
240 ms
;cfp=1;rndc=1504714240;noperf=1;alias=;cmd=bid;cors=yes
97 ms
;cfp=1;rndc=1504714239;noperf=1;alias=;cmd=bid;cors=yes
112 ms
;cfp=1;rndc=1504714239;noperf=1;alias=;cmd=bid;cors=yes
95 ms
;cfp=1;rndc=1504714240;noperf=1;alias=;cmd=bid;cors=yes
35 ms
AdCallAggregator
279 ms
symbolset-custom.woff
32 ms
770 ms
46 ms
47 ms
63 ms
62 ms
sourcesanspro-semibold.svgz
26 ms
sourcesanspro-semibold.woff
26 ms
sourcesanspro-bold.woff
47 ms
12 ms
6 ms
125 ms
5 ms
5 ms
7 ms
4 ms
6 ms
a977f616ddce7ad9d5f8b072ca753777afa5fefd
108 ms
c01932f06608b26faec0bfe099980b76f822d22d
105 ms
a6f3603a039b75612567d81ea06eef33184dfec4
107 ms
actions
57 ms
ActivityServer.bs
51 ms
ebAttribution.js
56 ms
171 ms
analytics.js
11 ms
gemini-synacor.js
385 ms
t.gif
71 ms
raven.min.js
13 ms
json
122 ms
257 ms
iframe.html
46 ms
up_loader.1.1.0.js
285 ms
fbevents.js
13 ms
8qphnx.js
68 ms
lb
321 ms
conversion.js
239 ms
xyz.js
276 ms
pxl.png
255 ms
tr
240 ms
track.gif
96 ms
track.gif
99 ms
track.gif
96 ms
pxl.png
276 ms
insight.min.js
253 ms
1636884449927537
47 ms
postmessage.min.js
73 ms
bk-coretag.js
161 ms
38 ms
eps
315 ms
183 ms
rightmedia
152 ms
pixel
176 ms
utsync.ashx
172 ms
cse
353 ms
3aadbb71016ecd7a194bbe2791777e9a.png
111 ms
408427ebca9b8b8a682eae402625df15.png
76 ms
2ac5fd0388becaf347b1ca964088df8f.jpg
77 ms
8b37adf20608eaa44e31b4208a3fae90.jpg
77 ms
d59204d3363465b76ab3a173a670df60.jpg
76 ms
%3Fapp%3Dportal%26sig%3D48add57365ba639191586c902db821d28579a8ebe483ba48027c34b5f221fa94
77 ms
%3Fapp%3Dportal%26sig%3D48add57365ba639191586c902db821d28579a8ebe483ba48027c34b5f221fa94
89 ms
%3Fapp%3Dportal%26sig%3D48add57365ba639191586c902db821d28579a8ebe483ba48027c34b5f221fa94
89 ms
%3Fapp%3Dportal%26sig%3D37b7c5982a55a90f5d6ae0eee39551fe5a6f51770cd66694ce349517479c28b7
97 ms
7f7b7be9f6a61f57e6a4142fadbe53300a5fb8ecb307637e6cad4023
94 ms
9ce4c57dbd50328380a0adcfd08c601d.jpg
95 ms
d1ce4661c0f84dbcf89e4ea0082ea5ce.jpg
93 ms
mediamind.html
55 ms
ActivityServer.bs
146 ms
up
40 ms
appnexus
27 ms
pixel
47 ms
ActivityServer.bs
34 ms
generic
29 ms
rtb-h
61 ms
universal_pixel.1.1.1.js
50 ms
receive
54 ms
s58670954166445
133 ms
g-d-min.js
59 ms
ssi
301 ms
up
54 ms
tr
35 ms
pxl.png
50 ms
pxl.png
50 ms
1636884449927537
31 ms
53 ms
pixel.gif
45 ms
eps
159 ms
143 ms
rtb-h
158 ms
32441
73 ms
17314
166 ms
rtset
121 ms
Pug
136 ms
379208.gif
79 ms
weathericons-regular-webfont.woff
79 ms
109 ms
362248.gif
93 ms
ep
385 ms
generic
53 ms
cm
1075 ms
60 ms
ermcm
117 ms
sd
259 ms
tap.php
40 ms
rtset
41 ms
379208.gif
33 ms
pixel
41 ms
tap.php
37 ms
sd
37 ms
Pug
48 ms
usersync.html
207 ms
pixel
67 ms
cm
27 ms
pixel.gif
12 ms
rightmedia
24 ms
pixel.gif
9 ms
2981
154 ms
cb-1500408837131-2435.javascript
3 ms
1502999552885-4698.jpg
109 ms
1498691777791-6991.jpg
109 ms
1489776997460-3506.jpg
111 ms
425b266c52478354ab381b7ae1eb4d02.jpeg
110 ms
1504136579700-1201.jpg
110 ms
84d12b9faec323f51c2d1e7ae0bc2a68.jpeg
113 ms
1478263215723-3291.jpg
112 ms
50bbb501fdfc089780d8e0a0c5068ea7.jpeg
112 ms
1501678575206-4378.jpg
115 ms
1500625570900-2229.jpg
115 ms
syndication@2x.png
108 ms
show_companion_ad.js
92 ms
ads
423 ms
3096
81 ms
77 ms
click
158 ms
osd_listener.js
82 ms
osd.js
53 ms
hls.light.min.js
253 ms
ima3.js
68 ms
click
266 ms
click
210 ms
l
276 ms
bridge3.178.0_en.html
130 ms
client.js
231 ms
aceUAC.js
145 ms
post_adtech
182 ms
generic
110 ms
ad
182 ms
AdId=5269378;BnId=1;ct=2514444091;st=86379;adcid=1;itime=714241405;reqtype=5;;
108 ms
112 ms
AdId=9083474;BnId=1;ct=2514500215;st=108054;adcid=1;itime=714241589;reqtype=5;;
56 ms
post_adtech
92 ms
bind
43 ms
e1be68bb5a771ade04690c208715e8f45f7a1fd8
94 ms
ffc2f15259853de9fd20da8fd79b00b51fe95468
94 ms
a076d57c45fd42bb948441d66962587cd943c4e5
93 ms
21351ea226756dfe736d4d3e95d51466afcf7458
96 ms
34b2cdbb7522b707a27cd6b7e371979578eb43f1
97 ms
b9b4e945c084afc1ea9b3b4eeca77c303b224081
96 ms
AdId=5069843;BnId=1;ct=2514500251;st=215534;adcid=1;itime=714241586;reqtype=5;;
86 ms
post_adtech
45 ms
evansville.net accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
[role]s do not have all required [aria-*] attributes
[aria-*] attributes do not have valid values
[aria-*] attributes are not valid or misspelled
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Definition list items are not wrapped in <dl> elements
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
evansville.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
evansville.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Evansville.net 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 Evansville.net 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.
evansville.net
Open Graph description is not detected on the main page of Evansville. 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: