5.3 sec in total
23 ms
4.5 sec
762 ms
Visit kezi.com now to see the best up-to-date KEZI content for United States and also check out these interesting facts you probably never knew about kezi.com
Eugene breaking news, weather and live video. Covering local politics, crime, health, education and sports for Eugene and the Willamette Valley in Oregon.
Visit kezi.comWe analyzed Kezi.com page load time and found that the first response time was 23 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
kezi.com performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value13.6 s
0/100
25%
Value28.8 s
0/100
10%
Value27,270 ms
0/100
30%
Value0.164
72/100
15%
Value92.8 s
0/100
10%
23 ms
66 ms
161 ms
147 ms
174 ms
Our browser made a total of 147 requests to load all elements on the main page. We found that 5% of them (7 requests) were addressed to the original Kezi.com, 44% (65 requests) were made to Bloximages.newyork1.vip.townnews.com and 9% (13 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Embed.secondstreetapp.com.
Page size can be reduced by 938.1 kB (34%)
2.7 MB
1.8 MB
In fact, the total size of Kezi.com main page is 2.7 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 1.7 MB which makes up the majority of the site volume.
Potential reduce by 478.4 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 65.6 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 478.4 kB or 87% of the original size.
Potential reduce by 0 B
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. KEZI images are well optimized though.
Potential reduce by 446.5 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 446.5 kB or 26% of the original size.
Potential reduce by 13.1 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. Kezi.com needs all CSS files to be minified and compressed as it can save up to 13.1 kB or 19% of the original size.
Number of requests can be reduced by 69 (53%)
131
62
The browser has sent 131 CSS, Javascripts, AJAX and image requests in order to completely render the main page of KEZI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 61 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
kezi.com
23 ms
www.kezi.com
66 ms
bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css
161 ms
layout.5bce7eb56c23d79d6ab89ab093c281ea.css
147 ms
theme-basic.a7351649a9c39f0af7c6d288a87ef140.css
174 ms
css2
115 ms
flex-weather-expandable.29365b27620977c8d65433d576ef0ca5.css
169 ms
tntslider.61e562ee97efb10698d15f5cee4962dc.css
172 ms
flex-utility-promo-button.52347555fbb6668223efabadb9c9d111.css
145 ms
access.d7adebba498598b0ec2c.js
39 ms
jquery.min.d6d18fcf88750a16d256e72626e676a6.js
171 ms
user.js
112 ms
bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js
208 ms
common.08a61544f369cc43bf02e71b2d10d49f.js
207 ms
tnt.ee95c0b6f1daceb31bf5ef84353968c6.js
207 ms
application.3c64d611e594b45dd35b935162e79d85.js
207 ms
polyfill.min.js
1103 ms
chartbeat_mab.js
129 ms
user-controls.578df3df79d812af55ab13bae47f9857.js
216 ms
tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js
207 ms
gpt.js
206 ms
tntslider.7177a362b66d47f546bd877a7efd6bd4.js
217 ms
tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js
220 ms
tracking.js
123 ms
fontawesome.568f3d1ab17b33ce05854081baadadac.js
223 ms
osano.js
134 ms
load.js
225 ms
6039a864-9622-4b9e-bf48-ec943f27297b.js
126 ms
tracker.js
126 ms
fuel.js
135 ms
optin.js
3149 ms
get.js
124 ms
delivery.js
132 ms
tnt.ads.core.ee10a41bfea60001b9edb7ab35e5c9e1.js
213 ms
wxwidget.loader.js
157 ms
embed.js
81 ms
gtm.js
61 ms
analytics.js
18 ms
gtm.js
56 ms
gtm.js
28 ms
publisher:getClientId
97 ms
destination
30 ms
collect
102 ms
collect
156 ms
collect
143 ms
gtm.js
89 ms
destination
114 ms
collect
20 ms
js
37 ms
apstag.js
155 ms
chartbeat.js
129 ms
connatix.player.js
292 ms
6a45e856-74ae-11ec-a79b-ffcc95d9fa25.png
103 ms
f5a9b432-74ad-11ec-996c-bfa2baaf00b0.png
102 ms
1e75534e-74ae-11ec-a245-ff7f0ae3af6b.png
104 ms
663a48af0763e.image.jpg
103 ms
663a2262c8beb.image.jpg
101 ms
663a381f0b309.image.jpg
101 ms
66398ed57b2b9.image.jpg
279 ms
66398ddfe9ea6.image.jpg
278 ms
66327e29702b6.image.jpg
277 ms
64409fd6bc7a9.image.jpg
278 ms
61b7769449b05.preview.jpg
277 ms
662ad5b80b8e0.preview.jpg
279 ms
65948e5b4d558.preview.jpg
285 ms
65948df6a4f19.preview.jpg
286 ms
61b7767349962.preview.jpg
283 ms
61b776a825e63.preview.jpg
283 ms
61968ee303f8c.preview.jpg
284 ms
66393169ec5ea.image.jpg
283 ms
649e05396bd98.image.jpg
317 ms
663918693d647.image.jpg
318 ms
64c9824c41677.image.jpg
316 ms
61a92ae312b7d.image.jpg
316 ms
65d7d3975a154.image.jpg
315 ms
651535cfd7f19.image.jpg
317 ms
650c7ef6369d0.image.jpg
337 ms
64daf99ae13ef.image.jpg
318 ms
64837c90e814a.image.png
338 ms
63f1983a91b20.image.jpg
337 ms
63d4909b39504.image.jpg
319 ms
62cfb9eb171b4.image.jpg
337 ms
6635819f46859.image.jpg
356 ms
650b5e323e988.image.jpg
356 ms
66394cf4dcc34.image.jpg
371 ms
621d6c71862c6.image.jpg
370 ms
65c42014a20b6.image.jpg
373 ms
61a9293a3c736.image.jpg
370 ms
pubads_impl.js
46 ms
tracker.gif
38 ms
analytics.min.js
213 ms
66342df578079.image.png
295 ms
663700ed53d54.image.jpg
292 ms
66313c8f5784c.image.jpg
296 ms
662809cfb6d20.image.jpg
293 ms
661ec8ad687dd.image.jpg
293 ms
66158e7171787.image.jpg
292 ms
KFOmCnqEu92Fr1Me5Q.ttf
217 ms
KFOlCnqEu92Fr1MmEU9vAw.ttf
255 ms
KFOlCnqEu92Fr1MmSU5vAw.ttf
275 ms
KFOlCnqEu92Fr1MmWUlvAw.ttf
273 ms
KFOlCnqEu92Fr1MmYUtvAw.ttf
275 ms
132916964
150 ms
660c49ff46366.image.png
121 ms
61a928ec38871.image.jpg
121 ms
637ea216e1859.image.jpg
120 ms
662af26100ba5.image.jpg
120 ms
66293fe98b75f.image.jpg
121 ms
f27ddf36-ad5f-11ed-a1c4-a78dc4efcc2b.png
130 ms
settings
39 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpfBJ.ttf
34 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyovBJ.ttf
21 ms
870.bundle.6e2976b75e60ab2b2bf8.js
41 ms
tsub-middleware.bundle.77315eced46c5ae4c052.js
41 ms
YA9Gr02F12Xkf5whdwKf11l0jbKkeidMTtZ5Yihg2SOY.ttf
120 ms
YA9Gr02F12Xkf5whdwKf11l0jbKkeidMTtZ5YihS2SOY.ttf
118 ms
YA9Gr02F12Xkf5whdwKf11l0jbKkeidMTtZ5Yii-3iOY.ttf
160 ms
YA9Gr02F12Xkf5whdwKf11l0jbKkeidMTtZ5YiiH3iOY.ttf
159 ms
AGSKWxUt2h1TNrDCIgxDw7NJERQYTKUIV6kAetJjEfCuwFQu_XSqGFsgIWhKyDYf1a6tGdyfmJklha8leJ4asmxDsjSvCRAdC3ah5OxdMPx-EAWUF68pZRZslc5fq6izOFtFtCMTMcvUrQ==
92 ms
uid2SecureSignal.js
215 ms
esp.js
116 ms
publishertag.ids.js
216 ms
esp.js
225 ms
encrypted-tag-g.js
332 ms
sync.min.js
217 ms
pubcid.min.js
217 ms
ob.js
233 ms
m
458 ms
map
77 ms
adframe.
30 ms
rum.js
33 ms
AGSKWxXYQxfBi6R1YI-ShN-gb8T3300VoOLKhCpE8gyuLeeeMQ2JAyoNB4UdI9s0mCknZ6Yu-0dHs0hgcR5piCADr9vYJa6bqYxt-3ZSn6-0GSgRxbmGmfbt1Y7BcpqQAI6DFZbG6Ny0xw==
50 ms
AGSKWxU08mRRJdp4hNScEU7JONHLz2DpUCpO5HhpMH3cbxSK2X0iPom07IrbkLX6462AzCcxDxYhz7hBTI7VI1-QnyMeywEH_SjBibQYZ03-p8Py-qw9p1Y5DnoS_YO3zR1gBE1xrj2mkQ==
51 ms
AGSKWxVh3tveQGZa0xVCm38m0S_lGZgZACz0Ry0LARZbp1ZOgejdiTlaJhJPrhqrbkAXlV1bVCBFvp_02jRG0bv9SMvvSDewX9shyT1H-yPsaV0PwWIH1rDlmuO5qtvCz3hQUEX1EU8WFA==
42 ms
262327
103 ms
2172611
95 ms
9799.jsx
113 ms
polyfill.min.js
1030 ms
tiny-slider.css
253 ms
one.js
138 ms
4854354
271 ms
css
187 ms
mab
195 ms
ping
203 ms
css
64 ms
7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e0.ttf
67 ms
7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e0.ttf
66 ms
kezi.com 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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
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
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
kezi.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Kezi.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 Kezi.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.
kezi.com
Open Graph data is detected on the main page of KEZI. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: