3.3 sec in total
132 ms
2 sec
1.2 sec
Click here to check amazing Gannett content for United States. Otherwise, check out these important facts you probably never knew about gannett.com
Gannett Co., Inc
Visit gannett.comWe analyzed Gannett.com page load time and found that the first response time was 132 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
gannett.com performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value10.6 s
0/100
25%
Value7.7 s
25/100
10%
Value260 ms
83/100
30%
Value0.065
97/100
15%
Value13.6 s
11/100
10%
132 ms
33 ms
9 ms
240 ms
339 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 7% of them (3 requests) were addressed to the original Gannett.com, 52% (24 requests) were made to Gannettdigital-static-web.s3.amazonaws.com and 20% (9 requests) were made to Gannett-cdn.com. The less responsive or slowest element that took the longest time to load (853 ms) relates to the external source Gannettdigital-static-web.s3.amazonaws.com.
Page size can be reduced by 992.6 kB (7%)
13.3 MB
12.3 MB
In fact, the total size of Gannett.com main page is 13.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. 55% of websites need less resources to load. Images take 12.4 MB which makes up the majority of the site volume.
Potential reduce by 19.3 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 19.3 kB or 76% of the original size.
Potential reduce by 372.2 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. Gannett images are well optimized though.
Potential reduce by 297.8 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 297.8 kB or 66% of the original size.
Potential reduce by 303.3 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. Gannett.com needs all CSS files to be minified and compressed as it can save up to 303.3 kB or 83% of the original size.
Number of requests can be reduced by 4 (11%)
38
34
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gannett. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
gannett.com
132 ms
www.gannett.com
33 ms
font-awesome.min.css
9 ms
main.css
240 ms
main.js
339 ms
logo-header.png
181 ms
menu-dk.png
187 ms
devices.png
189 ms
clock.png
202 ms
graph.png
300 ms
usa-today-gannett.png
301 ms
phoenix-gannett.png
300 ms
detroit-gannett.png
694 ms
rochester-gannett.png
333 ms
nashville-gannett.png
426 ms
asbury-park-gannett.png
424 ms
indy-gannett.png
425 ms
fort-myers-gannett.png
427 ms
home_01_Gannett-2600.jpg
723 ms
analytics.js
23 ms
2E35D5_0_0.woff
317 ms
2E35D5_4_0.woff
334 ms
2E35D5_2_0.woff
431 ms
gi.woff
290 ms
fontawesome-webfont.woff
5 ms
collect
93 ms
current
9 ms
collect
106 ms
635909986053996263-USP-News--Republican-Debate.jpg
84 ms
635909838735642880-AXX-SCALIA-SUPREME-COURT.jpg
73 ms
635908980149528070-ono-dufour-.jpg
126 ms
635905400406417227-USATSI-9102896.jpg
133 ms
B9320863552Z.1_20160209155729_000_G3TDDMEBF.1-0.jpg
150 ms
635908744734818743-CE18234.jpg
107 ms
635909615236490522-Fife-and-Forbes-MAIN.jpg
133 ms
635910385973820603-BUR20160214carthroughice2.jpg
144 ms
astacio.jpg
222 ms
home-01_2600.jpg
690 ms
home-02_2600.jpg
312 ms
home-03_2600.jpg
814 ms
home-04_2600.jpg
853 ms
vrzPDnoxFYM
61 ms
www-embed-player-vflZsBgOl.css
63 ms
www-embed-player.js
85 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
27 ms
ad_status.js
23 ms
gannett.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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
gannett.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
gannett.com SEO score
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
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gannett.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Gannett.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
gannett.com
Open Graph description is not detected on the main page of Gannett. 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: