2.6 sec in total
81 ms
1.8 sec
750 ms
Click here to check amazing Seattle Pi content for United States. Otherwise, check out these important facts you probably never knew about seattlepi.com
Seattle local news, traffic, weather, business news, sports, real estate, photos and events.
Visit seattlepi.comWe analyzed Seattlepi.com page load time and found that the first response time was 81 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
seattlepi.com performance score
name
value
score
weighting
Value8.6 s
0/100
10%
Value20.6 s
0/100
25%
Value54.2 s
0/100
10%
Value96,860 ms
0/100
30%
Value0.006
100/100
15%
Value128.5 s
0/100
10%
81 ms
54 ms
42 ms
6 ms
9 ms
Our browser made a total of 205 requests to load all elements on the main page. We found that 9% of them (18 requests) were addressed to the original Seattlepi.com, 14% (28 requests) were made to D29xw9s9x32j3w.cloudfront.net and 7% (14 requests) were made to Ww2.hdnux.com. The less responsive or slowest element that took the longest time to load (744 ms) relates to the external source Hearstnewspapers-d.openx.net.
Page size can be reduced by 3.3 MB (39%)
8.4 MB
5.1 MB
In fact, the total size of Seattlepi.com main page is 8.4 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 3.8 MB which makes up the majority of the site volume.
Potential reduce by 211.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. This page needs HTML code to be minified as it can gain 83.0 kB, which is 34% 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 211.6 kB or 86% of the original size.
Potential reduce by 22.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. Seattle Pi images are well optimized though.
Potential reduce by 2.5 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 2.5 MB or 66% of the original size.
Potential reduce by 582.6 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. Seattlepi.com needs all CSS files to be minified and compressed as it can save up to 582.6 kB or 89% of the original size.
Number of requests can be reduced by 86 (45%)
193
107
The browser has sent 193 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Seattle Pi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 65 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
seattlepi.com
81 ms
www.seattlepi.com
54 ms
loadAds.js
42 ms
global.less.allPages.r9.3.1.0.css
6 ms
global.allPages.r9.3.1.0.js
9 ms
hearst.js
77 ms
chartbeat_mab.js
7 ms
pointslocal.widgets.min.js
154 ms
pointslocal.widgets.min.css
166 ms
kf_pp_widget_seattle_pi.js
356 ms
embedcode.php
75 ms
global.bottom.r9.3.1.0.js
7 ms
GetJS
5 ms
apstag.js
71 ms
initDefineAds.js
3 ms
gpt.js
67 ms
callback=extractPid
76 ms
http%3A%2F%2Fwww.seattlepi.com
65 ms
json
84 ms
Bootstrap.js
28 ms
http%3A%2F%2Fwww.seattlepi.com
231 ms
24 ms
bid
86 ms
pubads_impl_147.js
204 ms
weatherSprite.svg
52 ms
core_breaking_now.jpg
65 ms
core_centerpiece_tab.jpg
182 ms
core_centerpiece_tab_small.jpg
156 ms
core_promo.jpg
169 ms
widgets.js
59 ms
pointslocal.hearst.css
113 ms
W10=
380 ms
core_centerpiece_tab_small.jpg
171 ms
core_centerpiece_tab_small.jpg
169 ms
core_package_small.jpg
167 ms
core_package_small.jpg
170 ms
core_package.jpg
169 ms
core_package_small.jpg
171 ms
core_promo.jpg
172 ms
core_promo.jpg
172 ms
core_package_small.jpg
173 ms
core_package.jpg
173 ms
core_package_small.jpg
172 ms
core_promo.jpg
49 ms
core_package_small.jpg
49 ms
core_promo.jpg
37 ms
core_package.jpg
37 ms
core_package_small.jpg
140 ms
core_promo.jpg
141 ms
core_package.jpg
140 ms
core_package_small.jpg
140 ms
core_promo.jpg
154 ms
core_package.jpg
155 ms
square_small.jpg
154 ms
core_package.jpg
155 ms
core_package.jpg
150 ms
core_package.jpg
160 ms
core_package.jpg
156 ms
core_package.jpg
160 ms
core_promo.jpg
160 ms
core_package_small.jpg
159 ms
core_package_small.jpg
160 ms
core_package.jpg
162 ms
core_package_small.jpg
142 ms
core_promo.jpg
142 ms
sprite.svg
35 ms
social_sprite.svg
115 ms
nav_sprite.svg
113 ms
logo.svg
121 ms
serverComponent.php
137 ms
173d6d476fcf058ab12fa04eb7ef1e81
22 ms
core_package_small.jpg
102 ms
LB-Zone-2
387 ms
ce56e0563cec2322494030b032242ad9
82 ms
like.php
280 ms
kfs_puzzles_palace_promo_widget.css
247 ms
analytics.js
357 ms
thomas-joseph.jpg
332 ms
classic-sudoku.jpg
504 ms
mahjongg-dimensions.jpg
329 ms
sheffer-crossword.jpg
328 ms
premier-crossword.jpg
331 ms
conceptis-battleships.jpg
327 ms
jigsaw-puzzle.jpg
354 ms
freecell-solitaire.jpg
354 ms
pyramid-solitaire.jpg
354 ms
core_package.jpg
180 ms
robotoslab-bold-webfont.woff
208 ms
Roboto-Bold-webfont.woff
167 ms
Roboto-Medium-webfont.woff
167 ms
f692f588819ae4441679a42218271906.js
163 ms
yieldbot.intent.js
204 ms
jpt
171 ms
jpt
169 ms
jpt
172 ms
jpt
168 ms
jpt
199 ms
jpt
199 ms
jpt
199 ms
jpt
264 ms
jpt
267 ms
jpt
199 ms
cygnus
401 ms
fastlane.json
414 ms
fastlane.json
414 ms
fastlane.json
412 ms
fastlane.json
366 ms
fastlane.json
287 ms
fastlane.json
411 ms
fastlane.json
535 ms
fastlane.json
544 ms
fastlane.json
587 ms
fastlane.json
543 ms
c52a1b52da65d2fc6923b08418ff4b8e.js
19 ms
61f5807d14082a4dddeeea3ffd170f16.js
20 ms
fef68175fc0e0a95e97d6951980ac4bc.js
19 ms
aa78d7c587aaee4d37aa60b8391808f0.js
55 ms
asset_sprite.svg
48 ms
p.js
131 ms
eyJjb3VudCI6MywiZmVhdHVyZWQiOiIxeCJ9
102 ms
4qFiRLLPSF7.js
122 ms
lH1ibRl5GKq.png
121 ms
arj
744 ms
c.js
84 ms
load.js
131 ms
async_usersync.html
55 ms
init
90 ms
image
268 ms
image
273 ms
image
319 ms
chartbeat.js
14 ms
like.php
57 ms
Roboto-Regular-webfont.woff
45 ms
embedplayer.php
109 ms
collect
53 ms
73 ms
ping
62 ms
4qFiRLLPSF7.js
72 ms
t
226 ms
css
140 ms
normalize.css
144 ms
desktop.css
141 ms
desktop.css
142 ms
jquery-1.11.1.min.js
145 ms
jwplayer.js
140 ms
jquery.mobile.custom.min.js
168 ms
purl.js
171 ms
streamsense.4.1505.18.min.js
172 ms
s2nvideocontroller20170616.js
169 ms
s2nComScoreRR20161201.js
170 ms
easing.js
176 ms
iscroll-probe.js
176 ms
jquery.dotdotdot.min.js
179 ms
common.js
179 ms
collect
77 ms
s04384390693157
134 ms
analytics.js
67 ms
hamburger.gif
63 ms
ajax-loader-dark-transparent.gif
65 ms
poweredby_light.png
64 ms
desktop.js
29 ms
social_sprite.svg
59 ms
hearst.svg
65 ms
data_read.php
68 ms
51 ms
N9KSa305HxlY5zk6XisHxw.ttf
51 ms
hFqlepBer-IXtJK7U5poifesZW2xOQ-xsNqO47m55DA.ttf
52 ms
container.html
43 ms
collect
35 ms
EADC8C5E62634F52B49DD5E682A2FFC1.jpg
392 ms
trk.gif
104 ms
5D4DD428717C4943862606970B50D0AD.gif
477 ms
trk.gif
92 ms
m63zywb6ou6k3jin7y1ce7gya9dpfb5c.jpg
228 ms
polyfills.promise.js
182 ms
1-q289s915rnq1p28159p4p9728q49992q.jpg
167 ms
667f31980082a9755da151aa56bb0a28.jpg
164 ms
1-53nrnq6n798pr3p3qn6r2129s630o6p7.jpg
165 ms
pqzvwdvb3p6jvtuw8a7p7cdbs8pev05w.jpg
169 ms
1-3nsrr15r847493snn49prpp48n7rq3sp.jpg
165 ms
1-91472864o604r1p0so8q281oor013364.jpg
171 ms
1-0992s9o7n20n08n8106nr4n40n50q48p.jpg
167 ms
l8kfc848wbaywzf7ofgrdcea112ia6y4.jpg
167 ms
m63zywb6ou6k3jin7y1ce7gya9dpfb5c.jpg
167 ms
json
181 ms
weather.json
169 ms
fbevents.js
93 ms
cc.js
90 ms
button.3ccb64e61d4c01fae12cd2b0ed9b2bab.js
134 ms
collect
101 ms
collect
160 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
85 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
87 ms
trk.gif
84 ms
beacon.js
147 ms
outbrain.js
122 ms
iu3
65 ms
trk.gif
63 ms
753932334760552
31 ms
pr
54 ms
jw-icons.woff
40 ms
31 ms
29 ms
follow_button.f8c8d971a6ac545cf416e3c1ad4bbc65.en.html
30 ms
ecm3
9 ms
seattlepi.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
[role]s do not have all required [aria-*] attributes
[role]s are not contained by their required parent element
[aria-*] attributes are not valid or misspelled
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
The document uses <meta http-equiv="refresh">
seattlepi.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
seattlepi.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
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 Seattlepi.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 Seattlepi.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.
seattlepi.com
Open Graph data is detected on the main page of Seattle Pi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: