22.8 sec in total
376 ms
22.2 sec
224 ms
Welcome to local.seattlepi.com homepage info - get ready to check Local Seattle Pi best content for United States right away, or after learning these important things about local.seattlepi.com
Find Business listings by category in Seattle, Washington. Get Business listings by category phone numbers, driving directions, business addresses, maps and more.
Visit local.seattlepi.comWe analyzed Local.seattlepi.com page load time and found that the first response time was 376 ms and then it took 22.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
local.seattlepi.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value3.9 s
52/100
25%
Value3.8 s
84/100
10%
Value280 ms
81/100
30%
Value0.025
100/100
15%
Value5.1 s
75/100
10%
376 ms
24 ms
38 ms
48 ms
30 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 7% of them (8 requests) were addressed to the original Local.seattlepi.com, 8% (9 requests) were made to Extras.seattlepi.com and 8% (9 requests) were made to Static.localedge.com. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Www2.mysanantonio.com.
Page size can be reduced by 724.4 kB (72%)
1.0 MB
285.4 kB
In fact, the total size of Local.seattlepi.com main page is 1.0 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. Javascripts take 690.4 kB which makes up the majority of the site volume.
Potential reduce by 52.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 22.2 kB, which is 36% 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 52.5 kB or 85% of the original size.
Potential reduce by 4.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. Obviously, Local Seattle Pi needs image optimization as it can save up to 4.2 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 466.9 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 466.9 kB or 68% of the original size.
Potential reduce by 200.8 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. Local.seattlepi.com needs all CSS files to be minified and compressed as it can save up to 200.8 kB or 87% of the original size.
Number of requests can be reduced by 84 (79%)
107
23
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Local 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 41 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
376 ms
layout.css
24 ms
jquery-ui-1.8.5.custom.css
38 ms
layout.css
48 ms
category.css
30 ms
category.css
47 ms
jquery-1.4.2.min.js
74 ms
jquery.history.js
45 ms
common.js
39 ms
jquery-ui-1.8.5.custom.min.js
104 ms
loadAdWiz.js
31 ms
Bootstrap.js
37 ms
common.css
12 ms
ga.js
22 ms
loadAdsMain.js
47 ms
__utm.gif
36 ms
GetJS
152 ms
GetJS
63 ms
gpt.js
66 ms
initDefineAds.js
14 ms
amzn_ads.js
157 ms
cc.js
236 ms
callback=extractPid
155 ms
hdm.js
162 ms
trinity.js
237 ms
yieldbot.intent.js
225 ms
banner-iframe.html
82 ms
header-slice.gif
101 ms
SeattlePIConnect.png
200 ms
serverComponent.php
99 ms
footer-iframe.html
98 ms
pubads_impl_83.js
188 ms
ui-bg_flat_100_ffffff_40x100.png
116 ms
acxiomlogo.jpg
116 ms
main.css
189 ms
sitelinks.js
359 ms
searchForm.js
357 ms
searchRadio.js
311 ms
mainNav.js
310 ms
bid
122 ms
footer.js
234 ms
c99e97accc34d01b26c13b762363e543.js
84 ms
cygnus
252 ms
usermatch
38 ms
usermatch
114 ms
GetJS
167 ms
GetJS
148 ms
__utm.gif
81 ms
dc.js
84 ms
c10014-pixel.js
77 ms
init
82 ms
container.html
56 ms
casale
57 ms
pixel
70 ms
usersync.aspx
466 ms
VwfyIsAoJYwAAS1AUJsAAADA%26961
104 ms
cm
54 ms
us.gif
56 ms
m
50 ms
hit.js
135 ms
casale
45 ms
44 ms
crum
116 ms
pixel
98 ms
callback=extractPid
91 ms
row2_tile.gif
88 ms
brand.png
89 ms
crum
163 ms
rum
75 ms
ads
530 ms
cygnus
254 ms
cygnus
261 ms
hearst_logo.png
208 ms
hearst125-logo-footer.png
221 ms
sync
198 ms
crum
186 ms
crum
184 ms
searchbox.png
103 ms
us.gif
96 ms
searchbutton.png
20211 ms
container.html
96 ms
bid
97 ms
bid
122 ms
us.gif
70 ms
us.gif
87 ms
pinav-list1.jpg
96 ms
pinav-list2.jpg
80 ms
subnav_delimiter.gif
85 ms
us.gif
35 ms
r2
20 ms
exchange
43 ms
crum
102 ms
expansion_embed.js
64 ms
4352205825735218299
71 ms
abg.js
84 ms
m_js_controller.js
95 ms
googlelogo_color_112x36dp.png
81 ms
osd.js
62 ms
s
38 ms
x_button_blue2.png
29 ms
push
87 ms
pixel
13 ms
activeview
34 ms
nr-918.min.js
348 ms
rt=ifr
30 ms
af06238595
62 ms
pixel
16 ms
g.json
61 ms
tpc=na_id
31 ms
usermatchredir
13 ms
a074291d4254a5c01308aa94d8f06f06
43 ms
5907
43 ms
tpid=VwfyIsAoJYwAASwAKGMAAAFg%26961
20 ms
21 ms
18 ms
tp=ANXS
15 ms
tpid=fc9d7270-24fa-5088-9faf-4571cf31b82e
8 ms
362738.gif
10 ms
tpidqp=tpid
5 ms
local.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Form elements do not have associated labels
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.
local.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
local.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
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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 Local.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 Local.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.
local.seattlepi.com
Open Graph description is not detected on the main page of Local Seattle Pi. 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: