2.4 sec in total
177 ms
1.7 sec
534 ms
Welcome to whodatdish.com homepage info - get ready to check Who Dat Dish best content for United States right away, or after learning these important things about whodatdish.com
Find the latest New Orleans Saints news, rumors, free agency, and draft updates, plus all things Joe Burrow brought to you by Who Dat Dish
Visit whodatdish.comWe analyzed Whodatdish.com page load time and found that the first response time was 177 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
whodatdish.com performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value5.7 s
17/100
25%
Value15.0 s
1/100
10%
Value5,640 ms
0/100
30%
Value0.15
76/100
15%
Value27.4 s
0/100
10%
177 ms
7 ms
17 ms
38 ms
15 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Whodatdish.com, 33% (28 requests) were made to Cdn.fansided.com and 7% (6 requests) were made to Wfpscripts.webspectator.com. The less responsive or slowest element that took the longest time to load (763 ms) relates to the external source Cdn.fansided.com.
Page size can be reduced by 920.6 kB (61%)
1.5 MB
576.4 kB
In fact, the total size of Whodatdish.com main page is 1.5 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. 70% of websites need less resources to load. Javascripts take 945.4 kB which makes up the majority of the site volume.
Potential reduce by 68.6 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 68.6 kB or 77% of the original size.
Potential reduce by 3.1 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. Who Dat Dish images are well optimized though.
Potential reduce by 656.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 656.5 kB or 69% of the original size.
Potential reduce by 192.4 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. Whodatdish.com needs all CSS files to be minified and compressed as it can save up to 192.4 kB or 83% of the original size.
Number of requests can be reduced by 49 (63%)
78
29
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Who Dat Dish. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and as a result speed up the page load time.
whodatdish.com
177 ms
wp-emoji-release.min.js
7 ms
fs-styles.css
17 ms
15.css
38 ms
tgx.js
15 ms
analytics.js
14 ms
gpt.js
9 ms
amzn_ads.js
48 ms
pql
54 ms
evidon.js
9 ms
abw.js
44 ms
fansided_s_code.js
274 ms
jquery.min.js
49 ms
fs-v557.min.js
39 ms
wp-embed.min.js
33 ms
pubads_impl_82.js
45 ms
collect
178 ms
collect
450 ms
c.js
223 ms
collect
186 ms
collect
445 ms
bid
215 ms
container.html
200 ms
i.js
271 ms
ads
372 ms
fansided_logo.png
154 ms
si_logo.png
62 ms
saints.png
67 ms
WDD_Header3_Large.jpg
71 ms
fs_logo.svg
66 ms
fansided.woff
68 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
65 ms
HqHm7BVC_nzzTui2lzQTDaCWcynf_cDxXwCLxiixG1c.ttf
140 ms
bH7276GfdCjMjApa_dkG6aCWcynf_cDxXwCLxiixG1c.ttf
141 ms
bleacher-report-15-96330.jpg
213 ms
bleacher-report-15-94592.jpg
214 ms
bleacher-report-15-26737.jpg
213 ms
bleacher-report-15-8170.jpg
212 ms
bleacher-report-15-81571.jpg
211 ms
bleacher-report-15-2180.jpg
211 ms
bleacher-report-15-83593.jpg
215 ms
bleacher-report-15-41603.jpg
214 ms
gk5FxslNkTTHtojXrkp-xJhsE6jcpsD2oq89kgohWx0.ttf
86 ms
moatad.js
306 ms
ws-D88C0B40.js
252 ms
adunitMapping
256 ms
ads
263 ms
beacon.js
327 ms
quant.js
283 ms
nick-fairley-nfl-detroit-lions-nick-fairley-trial-4-590x900.jpg
291 ms
init1.js
204 ms
;ord=1458283813033
169 ms
fsnews-jsp.json
763 ms
s67067058077082
120 ms
james-laurinaitis-nfl-st.-louis-rams-tampa-bay-buccaneers-415x250.jpg
45 ms
nate-stupar-nfl-washington-redskins-atlanta-falcons-415x250.jpg
46 ms
nick-fairley-nfl-st.-louis-rams-minnesota-vikings-850x560.jpg
100 ms
nfl-dallas-cowboys-new-orleans-saints-268x162.jpg
44 ms
fitzgerald-toussaint-jamarca-sanford-nfl-preseason-new-orleans-saints-baltimore-ravens-268x162.jpg
48 ms
MarchMadnessGiveaway2016_both-268x162.jpg
48 ms
bigarrow.svg
94 ms
osd.js
93 ms
ads
546 ms
init
47 ms
quantcast.js
44 ms
ws-ad.js
48 ms
pixel;r=522939799;a=p-dePfRmGlygL1o;fpan=1;fpa=P0-310064587-1458283813208;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458283813208;tzo=-180;ref=;url=http%3A%2F%2Fwhodatdish.com%2F;ogl=type.blog%2Ctitle.%20-%20A%20New%20Orleans%20Saints%20Fan%20Site%20-%20News%252C%20Blogs%252C%20Opinion%20and%20more%252E%2Curl.http%3A%2F%2F%2Cimage.https%3A%2F%2Fcdn%252Efansided%252Ecom%2Fwp-content%2Fassets%2Fsite_images%2F%2Fheaders%2F%2Csite_name.
33 ms
bcn
144 ms
initcb
12 ms
1x1.png
7 ms
ortc-2.1.24.js
6 ms
swfobject.js
5 ms
blockadblock.js
5 ms
ws-4.4.13i_cc.js
17 ms
pixel;r=1046978428;a=p-HGAVM7nQJ_sep;fpan=0;fpa=P0-310064587-1458283813208;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458283813288;tzo=-180;ref=;url=http%3A%2F%2Fwhodatdish.com%2F;ogl=type.blog%2Ctitle.%20-%20A%20New%20Orleans%20Saints%20Fan%20Site%20-%20News%252C%20Blogs%252C%20Opinion%20and%20more%252E%2Curl.http%3A%2F%2F%2Cimage.https%3A%2F%2Fcdn%252Efansided%252Ecom%2Fwp-content%2Fassets%2Fsite_images%2F%2Fheaders%2F%2Csite_name.
28 ms
12 ms
pixel;r=1033717839;a=p-HGAVM7nQJ_sep;fpan=0;fpa=P0-310064587-1458283813208;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458283813265;tzo=-180;ref=http%3A%2F%2Fwhodatdish.com%2F;url=http%3A%2F%2Fwhodatdish.com%2F;ogl=
7 ms
activeview
12 ms
activeview
15 ms
16_DIS_GA_728x90.jpg
55 ms
sbhK2lTE.js
44 ms
adunitMapping
24 ms
cTrvNaRi.html
12 ms
pixel;r=577873319;a=p-HGAVM7nQJ_sep;fpan=0;fpa=P0-310064587-1458283813208;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458283813740;tzo=-180;ref=http%3A%2F%2Fwhodatdish.com%2F;url=http%3A%2F%2Fwhodatdish.com%2F;ogl=
29 ms
whodatdish.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
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
whodatdish.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
whodatdish.com SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whodatdish.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 Whodatdish.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.
whodatdish.com
Open Graph description is not detected on the main page of Who Dat Dish. 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: