3.8 sec in total
459 ms
3.2 sec
149 ms
Welcome to games.washingtonpost.com homepage info - get ready to check Games Washingtonpost best content for United States right away, or after learning these important things about games.washingtonpost.com
Test your knowledge and skill with great puzzles, crosswords and games: The Washington Post Sunday crossword, The Washington Post TV crossword, washingtonpost.com's Daily crossword, Sudoku and many mo...
Visit games.washingtonpost.comWe analyzed Games.washingtonpost.com page load time and found that the first response time was 459 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
games.washingtonpost.com performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value13.3 s
0/100
25%
Value11.1 s
6/100
10%
Value4,790 ms
0/100
30%
Value0.535
14/100
15%
Value29.5 s
0/100
10%
459 ms
36 ms
51 ms
25 ms
49 ms
Our browser made a total of 155 requests to load all elements on the main page. We found that 5% of them (8 requests) were addressed to the original Games.washingtonpost.com, 21% (33 requests) were made to Cdn.arenaconnect.arkadiumhosted.com and 13% (20 requests) were made to Js.washingtonpost.com. The less responsive or slowest element that took the longest time to load (800 ms) relates to the external source Staticxx.facebook.com.
Page size can be reduced by 1.8 MB (50%)
3.5 MB
1.8 MB
In fact, the total size of Games.washingtonpost.com main page is 3.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. 85% 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 2.0 MB which makes up the majority of the site volume.
Potential reduce by 205.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 26.1 kB, which is 11% 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 205.5 kB or 84% of the original size.
Potential reduce by 81.0 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. Games Washingtonpost images are well optimized though.
Potential reduce by 1.4 MB
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 1.4 MB or 70% of the original size.
Potential reduce by 35.5 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. Games.washingtonpost.com needs all CSS files to be minified and compressed as it can save up to 35.5 kB or 86% of the original size.
Number of requests can be reduced by 85 (56%)
153
68
The browser has sent 153 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Games Washingtonpost. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 59 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
games.washingtonpost.com
459 ms
css
36 ms
js
51 ms
js
25 ms
combo
49 ms
jquery-1.7.1.js
13 ms
twp-internal.js
12 ms
plugin.jquery.wp-preroll.min.js
11 ms
fb.js
261 ms
style.en-US.css
294 ms
recaptcha_ajax.js
174 ms
combo
230 ms
combo
265 ms
combo
267 ms
combo
223 ms
combo
245 ms
combo
266 ms
combo
258 ms
loader.min.js
146 ms
audsci.js
195 ms
wapolabs-partners.js
197 ms
quantcast.js
189 ms
main.js
266 ms
moatcontent.js
186 ms
em.js
172 ms
washington-post.jpg
24 ms
avatar_000.jpg
135 ms
146x80.png
134 ms
146x80.png
63 ms
146x80.png
133 ms
146x80.png
65 ms
146x80.png
130 ms
146x80.png
171 ms
660x300.jpg
23 ms
660x300.jpg
404 ms
660x300.png
60 ms
640x295%5B1%5D.jpg
20 ms
660x300.png
39 ms
146x80.png
37 ms
146x80.png
37 ms
146x80.png
29 ms
146x80.png
31 ms
146x80.png
34 ms
146x80.png
29 ms
146x80.png
34 ms
146x80.jpg
35 ms
146x80.png
34 ms
146x80.png
42 ms
all.js
181 ms
widgets.js
19 ms
ARK_mainNavigation_delim.png
73 ms
field_corner.png
75 ms
field.png
117 ms
connectLoader.gif
76 ms
slider.next.png
58 ms
ARK_newLable_R.png
80 ms
slider.prev.png
80 ms
slider.pagericon.png
80 ms
dbg52463.moatads.com
17 ms
492 ms
xd_arbiter.php
417 ms
xd_arbiter.php
800 ms
ad-sprite.png
109 ms
pixel;r=38879059;ns=0;url=http%3A%2F%2Fgames.washingtonpost.com%2F;ref=;et=1456835271463;a=p-5cYn7dCzvaeyA
60 ms
ga.js
76 ms
beacon.js
72 ms
krux-desktop-control.js
37 ms
swfobject.js
420 ms
amzn_ads.js
352 ms
info
429 ms
wp.css
29 ms
jstag
345 ms
controltag
671 ms
__utm.gif
192 ms
179 ms
pwapi.washingtonpost.com
520 ms
chartbeat.js
393 ms
combo
134 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
485 ms
star-on.png
71 ms
star-off.png
70 ms
star-half.png
387 ms
abp.gif
348 ms
wp.min.js
343 ms
bid
383 ms
abp.gif
340 ms
combo
350 ms
iui3
351 ms
avatar_034.jpg
533 ms
avatar_010.jpg
363 ms
avatar_054.jpg
305 ms
avatar_006.jpg
312 ms
avatar_048.jpg
311 ms
avatar_026.jpg
313 ms
avatar_041.jpg
346 ms
avatar_025.jpg
344 ms
avatar_011.jpg
362 ms
avatar_030.jpg
561 ms
avatar_019.jpg
377 ms
avatar_046.jpg
371 ms
avatar_028.jpg
376 ms
avatar_004.jpg
384 ms
lb_select.png
383 ms
arrows_pc.png
384 ms
ping
57 ms
xd_arbiter.php
254 ms
pubads_impl_81.js
38 ms
controltag.js.3269b976cac0388f80dbfdb09d96a4e7
223 ms
rta.js
213 ms
plugin.js
206 ms
like.php
241 ms
combo
193 ms
1
135 ms
sync
132 ms
i.js
306 ms
sync
289 ms
sync
283 ms
sync
288 ms
container.html
279 ms
vpc6VNjRPXV.js
559 ms
LVx-xkvaJ0b.png
616 ms
ads
322 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
194 ms
combo
82 ms
rud
57 ms
s26052052697632
129 ms
js
109 ms
save
137 ms
proxy
53 ms
proxy
52 ms
spacer.gif
39 ms
global-header-autocomplete.css
30 ms
combo
56 ms
jquery-ui.css
90 ms
jquery-ui.min.js
144 ms
acj
544 ms
acj
428 ms
MastheadSprite4.png
56 ms
osd.js
24 ms
jot
268 ms
postonidisplay-regular-webfont.ttf
35 ms
saveLatency
196 ms
ui-bg_flat_75_ffffff_40x100.png
86 ms
ui-bg_highlight-soft_75_cccccc_1x100.png
179 ms
ui-bg_glass_75_e6e6e6_1x400.png
180 ms
js
122 ms
style.3.3.min.css
25 ms
interstitial.3.3.min.js
62 ms
imgad
55 ms
wp_int_header_left.gif
11 ms
ads
72 ms
html_inpage_rendering_lib_200_121.js
43 ms
saveLatency
86 ms
moatad.js
13 ms
ads
67 ms
games.washingtonpost.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
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>).
games.washingtonpost.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
Page has valid source maps
games.washingtonpost.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Games.washingtonpost.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 Games.washingtonpost.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.
games.washingtonpost.com
Open Graph data is detected on the main page of Games Washingtonpost. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: