2.3 sec in total
370 ms
1.3 sec
642 ms
Welcome to wjrt.com homepage info - get ready to check WJRT best content right away, or after learning these important things about wjrt.com
Flint breaking news, weather and live video. Covering local politics, crime, health, education and sports for Flint, Saginaw, Bay City and Midland
Visit wjrt.comWe analyzed Wjrt.com page load time and found that the first response time was 370 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
wjrt.com performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value12.0 s
0/100
25%
Value26.0 s
0/100
10%
Value13,830 ms
0/100
30%
Value0.175
69/100
15%
Value62.6 s
0/100
10%
370 ms
73 ms
7 ms
122 ms
9 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Wjrt.com, 5% (3 requests) were made to Abc12.com and 3% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (370 ms) relates to the external source Abc12.com.
Page size can be reduced by 488.1 kB (43%)
1.1 MB
647.5 kB
In fact, the total size of Wjrt.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. 55% of websites need less resources to load. Javascripts take 615.6 kB which makes up the majority of the site volume.
Potential reduce by 123.9 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 21.2 kB, which is 13% 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 123.9 kB or 78% of the original size.
Potential reduce by 39.8 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. Obviously, WJRT needs image optimization as it can save up to 39.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 324.4 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 324.4 kB or 53% of the original size.
Number of requests can be reduced by 13 (23%)
57
44
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WJRT. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
www.abc12.com
370 ms
R_CSS.css
73 ms
jquery.min.js
7 ms
bootstrap.js
122 ms
addthis_widget.js
9 ms
outbrain.js
21 ms
dc.js
36 ms
gpt.js
24 ms
__utm.gif
13 ms
pubads_impl_82.js
7 ms
container.html
141 ms
s
316 ms
all.js
128 ms
app_store_header_2013_revised.png
224 ms
play_store_header_2013_revised.png
168 ms
moms_header_2013_revised.png
182 ms
enews_header_2013_revised.png
152 ms
HeaderImage_400x100_whitebar.jpg
153 ms
Hip+Hop+4+Flint.jpg
154 ms
Spring_Home_Garden_Show_Web_Ad-01-01.jpg
155 ms
firebirds0501515.jpg
155 ms
Michigan+State+Police.jpg
156 ms
Snyder+2+17.jpg
156 ms
flintwateremergency.jpg
158 ms
DEWEY+STREET+SHOOTING.jpg
156 ms
Genesee+Health+Department.PNG
158 ms
st.+pats+day.jpg
159 ms
bridal+show4.jpg
159 ms
housing35.jpg
161 ms
demott1.jpg
162 ms
least+testing+event.jpg
161 ms
bridal+show+preview.jpg
162 ms
hip+hop8.jpg
169 ms
.com+generic1.jpg
163 ms
vote2016.png
173 ms
newset.jpg
169 ms
obama+speaking+whitehouse.jpg
169 ms
flintwaterlatest.jpg
172 ms
water228.jpg
172 ms
gold+coin5.jpg
173 ms
FirstAlertHD_headerbox.jpg
174 ms
wx_97.png
178 ms
Hurley-88x47.gif
176 ms
BabyChangers_Web_16X9_300.jpg
176 ms
ABC12-everywhere-sponsored-Revised-3-26-15.jpg
176 ms
SchoolClosings_Sponsor_315x176.jpg
176 ms
graylogo.png
176 ms
ads
327 ms
glyphicons-halflings-white.png
125 ms
glyphicons-halflings.png
121 ms
265 ms
xd_arbiter.php
34 ms
xd_arbiter.php
169 ms
widgets.js
167 ms
beacon.js
130 ms
quant.js
125 ms
count.js
138 ms
300lo.json
106 ms
wjrt.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.
wjrt.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
wjrt.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 Wjrt.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 Wjrt.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.
wjrt.com
Open Graph data is detected on the main page of WJRT. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: