3 sec in total
179 ms
2.2 sec
617 ms
Welcome to qctoday.com homepage info - get ready to check Qctoday best content right away, or after learning these important things about qctoday.com
Read breaking news, sports and events from Davenport, Bettendorf, Moline, Rock Island and the the Quad Cities Region of Iowa and Illinois.
Visit qctoday.comWe analyzed Qctoday.com page load time and found that the first response time was 179 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
qctoday.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value11.9 s
0/100
25%
Value20.7 s
0/100
10%
Value14,060 ms
0/100
30%
Value0.878
3/100
15%
Value48.8 s
0/100
10%
179 ms
34 ms
59 ms
69 ms
53 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Qctoday.com, 15% (16 requests) were made to Qctimes.com and 8% (9 requests) were made to Match.adsrvr.org. The less responsive or slowest element that took the longest time to load (553 ms) relates to the external source 14000746.fls.doubleclick.net.
Page size can be reduced by 537.5 kB (42%)
1.3 MB
755.8 kB
In fact, the total size of Qctoday.com 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. 75% 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 659.7 kB which makes up the majority of the site volume.
Potential reduce by 472.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. This page needs HTML code to be minified as it can gain 93.2 kB, which is 18% 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 472.5 kB or 90% of the original size.
Potential reduce by 78 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. Qctoday images are well optimized though.
Potential reduce by 49.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. This website has mostly compressed JavaScripts.
Potential reduce by 15.7 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. Qctoday.com needs all CSS files to be minified and compressed as it can save up to 15.7 kB or 20% of the original size.
Number of requests can be reduced by 64 (78%)
82
18
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qctoday. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
qctimes.com
179 ms
bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css
34 ms
layout.b46cef82bac6c2a77ca1f12b4c79fc8a.css
59 ms
lee.ds.css
69 ms
flex-notification-controls.e115619c5ab5d4eb38fbd29cc0d2ea9b.css
53 ms
owl.carousel.d631cca58a0d014854c4a6c1815f1da3.css
62 ms
access.d7adebba498598b0ec2c.js
66 ms
osano.js
73 ms
jquery.min.d6d18fcf88750a16d256e72626e676a6.js
59 ms
user.js
103 ms
bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js
59 ms
common.08a61544f369cc43bf02e71b2d10d49f.js
59 ms
tnt.ee95c0b6f1daceb31bf5ef84353968c6.js
59 ms
application.3c64d611e594b45dd35b935162e79d85.js
64 ms
polyfill.min.js
64 ms
apstag.js
90 ms
tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js
88 ms
qctimes.com.js
102 ms
owl.carousel.50dc41fa734414148ce4b489fd904c5f.js
88 ms
tnt.notify.a814fe612f2dcba9061edc229aeaf90b.js
85 ms
tnt.notify.panel.bacbeac9a1ca6ee75b79b21a0e2e99f2.js
85 ms
firebase-app.js
69 ms
firebase-messaging.js
87 ms
messaging.js
274 ms
tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js
84 ms
tracking.js
131 ms
prebid7.9.0.js
129 ms
lee.common.js
127 ms
fontawesome.568f3d1ab17b33ce05854081baadadac.js
128 ms
tracker.js
130 ms
op.js
98 ms
qctimes.com.js
97 ms
dfp.lazy.pbjs.js
68 ms
gtm.js
295 ms
gtm.js
301 ms
5b8089cc-7d85-11ec-a279-5bf4714fbc58.png
201 ms
tracker.gif
143 ms
%7B%7Bimage%7D%7D
143 ms
user_no_avatar.82c8fc38eb25dca10493a994ca1bfb90.png
141 ms
logo-tagline.png
83 ms
ilad-logo.png
83 ms
serif-ds.woff
68 ms
34 ms
analytics.js
76 ms
gtm.js
69 ms
gtm.js
69 ms
62 ms
72 ms
fbevents.js
271 ms
5b5dc540-ca6c-013a-51e3-0cc47a8ffaac
163 ms
js
145 ms
bundle.js
388 ms
p.js
221 ms
a-012l.min.js
266 ms
bat.js
257 ms
107 ms
linkid.js
96 ms
publisher:getClientId
351 ms
iframe
452 ms
activityi;src=14000746;type=retar0;cat=quadc000;ord=3234287309670;npa=0;auiddc=470163884.1708261006;pscdl=noapi;gtm=45He42e0v6749731za200;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fqctimes.com%2F
553 ms
analytics.min.js
428 ms
destination
135 ms
360 ms
97029838.js
102 ms
85 ms
ml.gz.js
146 ms
collect
189 ms
collect
242 ms
collect
234 ms
collect
233 ms
97029838
212 ms
i
87 ms
settings
15 ms
67 ms
cksync.php
346 ms
ajs-destination.bundle.13362ca512563a10e34d.js
29 ms
up.js
36 ms
src=14000746;type=retar0;cat=quadc000;ord=3234287309670;npa=0;auiddc=*;pscdl=noapi;gtm=45He42e0v6749731za200;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fqctimes.com%2F
105 ms
ga-audiences
50 ms
30 ms
schemaFilter.bundle.f63551a29dc1697f71b6.js
14 ms
j
12 ms
m
367 ms
a-012l
56 ms
baker
86 ms
clarity.js
17 ms
sync
103 ms
generic
37 ms
73 ms
usersync.aspx
45 ms
35759
14 ms
9 ms
24 ms
sync
15 ms
sync
16 ms
pixel
71 ms
live_intent_sync
94 ms
generic
4 ms
generic
3 ms
generic
4 ms
generic
4 ms
sync
48 ms
generic
6 ms
generic
4 ms
generic
5 ms
generic
3 ms
52164
5 ms
c.gif
8 ms
qctoday.com accessibility score
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
qctoday.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 Qctoday.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 Qctoday.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.
qctoday.com
Open Graph data is detected on the main page of Qctoday. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: