3.1 sec in total
304 ms
2.5 sec
302 ms
Visit seattleweekly.com now to see the best up-to-date Seattle Weekly content for India and also check out these interesting facts you probably never knew about seattleweekly.com
Sign Up For Our Newsletters Subscribe to our e-mail newsletter to receive updates. Sign Up Marketplace
Visit seattleweekly.comWe analyzed Seattleweekly.com page load time and found that the first response time was 304 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.
seattleweekly.com performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value16.9 s
0/100
25%
Value16.7 s
0/100
10%
Value21,050 ms
0/100
30%
Value0.038
100/100
15%
Value36.3 s
0/100
10%
304 ms
63 ms
115 ms
227 ms
121 ms
Our browser made a total of 162 requests to load all elements on the main page. We found that 36% of them (58 requests) were addressed to the original Seattleweekly.com, 11% (18 requests) were made to Seattleweekly.platypost.net and 9% (15 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (652 ms) relates to the external source Scontent.xx.fbcdn.net.
Page size can be reduced by 1.0 MB (33%)
3.1 MB
2.1 MB
In fact, the total size of Seattleweekly.com main page is 3.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. 70% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 111.2 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 50.5 kB, which is 40% 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 111.2 kB or 88% of the original size.
Potential reduce by 62.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. Seattle Weekly images are well optimized though.
Potential reduce by 655.0 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 655.0 kB or 65% of the original size.
Potential reduce by 213.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. Seattleweekly.com needs all CSS files to be minified and compressed as it can save up to 213.7 kB or 87% of the original size.
Number of requests can be reduced by 68 (44%)
155
87
The browser has sent 155 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Seattle Weekly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
seattleweekly.com
304 ms
default-36346.css
63 ms
home-index-36346.css
115 ms
default-36346.js
227 ms
news-index-36346.js
121 ms
embed.php
123 ms
jquery.mousewheel-3.0.4.pack.js
119 ms
jquery.fancybox-1.3.4.js
118 ms
analytics.js
16 ms
gpt.js
7 ms
count.js
30 ms
prum.min.js
29 ms
gtm.js
29 ms
all.js
284 ms
citylogo-lg.png
97 ms
webfont.js
27 ms
logo_sound.png
98 ms
newNavBar.png
87 ms
inputBack.png
91 ms
button-search-glass.png
91 ms
newNav-news.png
92 ms
newNav-music.png
92 ms
newNav-restaurants.png
160 ms
newNav-arts.png
159 ms
newNav-film.png
159 ms
newNav-bestof.png
146 ms
newNav-promotions.png
145 ms
newNav-classifieds.png
160 ms
newSubNav.png
223 ms
icon-16-facebook.png
231 ms
icon-16-twitter.png
232 ms
icon-16-foursquare.png
230 ms
dt.common.streams.StreamServer.cls
228 ms
dt.common.streams.StreamServer.cls
229 ms
dt.common.streams.StreamServer.cls
266 ms
dt.common.streams.StreamServer.cls
266 ms
dt.common.streams.StreamServer.cls
275 ms
dt.common.streams.StreamServer.cls
274 ms
dt.common.streams.StreamServer.cls
274 ms
dt.common.streams.StreamServer.cls
301 ms
dt.common.streams.StreamServer.cls
344 ms
dt.common.streams.StreamServer.cls
342 ms
dt.common.streams.StreamServer.cls
342 ms
dt.common.streams.StreamServer.cls
344 ms
dt.common.streams.StreamServer.cls
342 ms
dt.common.streams.StreamServer.cls
346 ms
dt.common.streams.StreamServer.cls
405 ms
dt.common.streams.StreamServer.cls
407 ms
dt.common.streams.StreamServer.cls
452 ms
dt.common.streams.StreamServer.cls
406 ms
dt.common.streams.StreamServer.cls
406 ms
dt.common.streams.StreamServer.cls
461 ms
pubads_impl_81.js
27 ms
collect
18 ms
css
61 ms
collect
90 ms
quant.js
47 ms
collect
105 ms
collect
45 ms
ads
169 ms
container.html
28 ms
dt.common.streams.StreamServer.cls
380 ms
dt.common.streams.StreamServer.cls
387 ms
dt.common.streams.StreamServer.cls
386 ms
dt.common.streams.StreamServer.cls
387 ms
dt.common.streams.StreamServer.cls
384 ms
pixel;r=301664439;a=p-9eMdqgZDb7EWs;fpan=1;fpa=P0-106032723-1456749220210;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456749220210;tzo=-180;ref=;url=http%3A%2F%2Fseattleweekly.com%2F;ogl=site_name.Seattle%20Weekly%2Curl.http%3A%2F%2Fseattleweekly%252Ecom%2F
31 ms
Q_pTky3Sc3ubRibGToTAYjnFfol0SnfBMmbnmUK0fZM.ttf
31 ms
dt.common.streams.StreamServer.cls
384 ms
1-4
126 ms
ga-audiences
65 ms
style.css.php
25 ms
logo.png
68 ms
t_1456361049.533433.jpg
92 ms
jquery.fancybox-1.3.4.css
68 ms
jquery.fancybox-1.3.4.pack.js
66 ms
ga.js
23 ms
button_view.png
85 ms
t_1456360265.97427.jpg
90 ms
t_1456360469.723466.jpg
88 ms
t_1456360396.408279.jpg
88 ms
ga-audiences
86 ms
dt.common.streams.StreamServer.cls
383 ms
dt.common.streams.StreamServer.cls
375 ms
dt.common.streams.StreamServer.cls
371 ms
dt.common.streams.StreamServer.cls
371 ms
dt.common.streams.StreamServer.cls
373 ms
__utm.gif
16 ms
dt.common.streams.StreamServer.cls
358 ms
likebox.php
143 ms
bg.jpg
11 ms
ribbon_left.png
13 ms
ribbon_center.png
12 ms
ribbon_right.png
11 ms
leftside.png
12 ms
top.png
13 ms
rightside.png
14 ms
bottom.png
14 ms
dt.common.streams.StreamServer.cls
351 ms
dt.common.streams.StreamServer.cls
355 ms
diagonals.png
355 ms
bg.jpg
9 ms
mediaelementplayer.min.css
78 ms
friends2follow_socialstack.css
79 ms
social.css
114 ms
css
25 ms
12794394_1005648589504974_2472521138687470366_n.jpg
442 ms
10372003_10154022001373112_8441541134936618879_n.jpg
106 ms
Screen-Shot-2015-10-07-at-9.05.19-PM-300x300.png
222 ms
image.jpg
260 ms
jquery.min.js
74 ms
mediaelement-and-player.min.js
165 ms
friends2follow_socialstack.min.js
164 ms
482x320.png
120 ms
38x38.png
121 ms
480x320.png
121 ms
429x225.png
208 ms
130x130.png
218 ms
476x476.png
218 ms
3641431446370243107
77 ms
osd.js
42 ms
40 ms
xd_arbiter.php
597 ms
xd_arbiter.php
434 ms
xYm_UD1pmAz.css
301 ms
TGpOWuX6Pv8.css
385 ms
xPdT2kQG4vz.css
504 ms
_rx8naC75Dy.js
637 ms
x5F9OMjKyLw.js
649 ms
ICDbTSzjQEg.js
520 ms
TTCre3391I0.js
521 ms
facebook.png
100 ms
friends2follow_socialstack_responsive.min.js
41 ms
f2fi.php
58 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
12 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
12 ms
masonry.pkgd.min.js
42 ms
friends2follow_infinitescroll.min.js
41 ms
blank.gif
40 ms
12049493_1005656092837557_5863818514666126810_n.jpg
344 ms
12718268_1002952443107922_2651626673649070539_n.jpg
395 ms
12512462_1005655002837666_1437082807986034363_n.jpg
535 ms
12321595_913468422085775_6177006800958721483_n.jpg
531 ms
11924774_825206107578674_2650061750452982910_n.png
533 ms
5425_10154056065494866_7850765178574173209_n.jpg
590 ms
548327_10150705104054866_1390119664_n.jpg
527 ms
12321665_176539042724602_4482621886667215584_n.jpg
526 ms
558990_10203788267210371_78866354_n.jpg
583 ms
10923585_10153530089224942_7023629012996417792_n.jpg
584 ms
12046921_1699926503609036_865769366253078849_n.jpg
588 ms
12805722_114675212257879_7410465563210972975_n.jpg
591 ms
399667_10152055611045203_572689381_n.jpg
592 ms
12642560_10153903368142485_3836604291165156910_n.jpg
651 ms
11698683_926566593110_5649056071300829353_n.jpg
652 ms
HEyyDkPknAC.png
72 ms
wL6VQj7Ab77.png
71 ms
s7jcwEQH7Sx.png
69 ms
activeview
13 ms
I6-MnjEovm5.js
70 ms
vlXaquuXMrr.js
135 ms
beacon.gif
68 ms
xd_arbiter.php
203 ms
seattleweekly.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-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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
seattleweekly.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
Issues were logged in the Issues panel in Chrome Devtools
seattleweekly.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
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 Seattleweekly.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 Seattleweekly.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.
seattleweekly.com
Open Graph description is not detected on the main page of Seattle Weekly. 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: