6.8 sec in total
1.5 sec
4.5 sec
764 ms
Visit phinneywood.com now to see the best up-to-date Phinney Wood content for United States and also check out these interesting facts you probably never knew about phinneywood.com
A news blog for Seattle's Phinney Ridge and Greenwood neighborhoods
Visit phinneywood.comWe analyzed Phinneywood.com page load time and found that the first response time was 1.5 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
phinneywood.com performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value4.2 s
44/100
25%
Value3.0 s
94/100
10%
Value460 ms
61/100
30%
Value0.044
99/100
15%
Value6.7 s
56/100
10%
1462 ms
112 ms
750 ms
766 ms
19 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 38% of them (41 requests) were addressed to the original Phinneywood.com, 11% (12 requests) were made to Static.xx.fbcdn.net and 11% (12 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Phinneywood.com.
Page size can be reduced by 435.5 kB (45%)
959.2 kB
523.7 kB
In fact, the total size of Phinneywood.com main page is 959.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Javascripts take 381.7 kB which makes up the majority of the site volume.
Potential reduce by 74.8 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 74.8 kB or 78% of the original size.
Potential reduce by 2.4 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. Phinney Wood images are well optimized though.
Potential reduce by 248.8 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 248.8 kB or 65% of the original size.
Potential reduce by 109.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. Phinneywood.com needs all CSS files to be minified and compressed as it can save up to 109.6 kB or 83% of the original size.
Number of requests can be reduced by 60 (60%)
100
40
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phinney Wood. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.phinneywood.com
1462 ms
style.css
112 ms
map_style.css
750 ms
custom.css
766 ms
google_service.js
19 ms
bbpress.css
126 ms
events_manager.css
124 ms
postratings-css.css
111 ms
jetpack.css
191 ms
jquery.js
192 ms
jquery-migrate.min.js
173 ms
core.min.js
167 ms
widget.min.js
211 ms
position.min.js
216 ms
mouse.min.js
231 ms
sortable.min.js
232 ms
datepicker.min.js
291 ms
menu.min.js
276 ms
autocomplete.min.js
281 ms
resizable.min.js
281 ms
draggable.min.js
320 ms
button.min.js
326 ms
dialog.min.js
326 ms
events-manager.js
372 ms
photon.js
306 ms
editor.js
310 ms
postratings-js.js
307 ms
devicepx-jetpack.js
57 ms
gprofiles.js
60 ms
wpgroho.js
350 ms
wp-embed.min.js
351 ms
e-201609.js
5 ms
google_ads.js
17 ms
header_1.jpg%22%20width=%22970%22%20height=%22140%22%20alt=%22PhinneyWood
988 ms
header_2.jpg%22%20width=%22970%22%20height=%22140%22%20alt=%22PhinneyWood
986 ms
header_3.jpg%22%20width=%22970%22%20height=%22140%22%20alt=%22PhinneyWood
982 ms
header_4.jpg%22%20width=%22970%22%20height=%22140%22%20alt=%22PhinneyWood
981 ms
header_5.jpg%22%20width=%22970%22%20height=%22140%22%20alt=%22PhinneyWood
979 ms
wp-emoji-release.min.js
133 ms
phinneywood_logo_300x50.jpg
122 ms
hr_dot_black.gif
170 ms
header_1.jpg
285 ms
ads
74 ms
new_twitter.jpg
147 ms
Aurora_87th.jpg
328 ms
Dr-Seuss-sign-resized.jpg
14 ms
Read-Across-America-sign-resized.jpg
11 ms
Woman-stealing-shoes-resized2.jpg
13 ms
phinneywood-restaurants.jpg
234 ms
new_facebook.jpg
146 ms
new_rss.jpg
150 ms
ads
31 ms
facebook_share_icon.gif
17 ms
hr_title_sep.gif
219 ms
hr_tag_sep.gif
265 ms
ads
30 ms
osd.js
9 ms
likebox.php
140 ms
like.php
128 ms
ads
35 ms
like.php
112 ms
like.php
107 ms
24730020030_f1931fd432_m.jpg
46 ms
ads
35 ms
like.php
116 ms
like.php
110 ms
like.php
151 ms
like.php
139 ms
like.php
154 ms
like.php
158 ms
24155180999_42dd2c3e92_m.jpg
9 ms
ads
39 ms
vpc6VNjRPXV.js
522 ms
LVx-xkvaJ0b.png
523 ms
16902003690_ec95533c90_m.jpg
109 ms
ads
32 ms
jTuqQ-OPDr6.css
555 ms
n370yiaI2G6.css
594 ms
_rx8naC75Dy.js
639 ms
x5F9OMjKyLw.js
669 ms
ICDbTSzjQEg.js
602 ms
TTCre3391I0.js
602 ms
24278130923_d814452c81_m.jpg
18 ms
ads
42 ms
24796723665_900d719a68_m.jpg
20 ms
ads
32 ms
rating_over.gif
376 ms
all.js
380 ms
g.gif
4 ms
ga.js
29 ms
hovercard.css
71 ms
services.css
91 ms
__utm.gif
69 ms
__utm.gif
73 ms
80 ms
xd_arbiter.php
193 ms
xd_arbiter.php
323 ms
521799_10150650882188141_1738100522_n.jpg
216 ms
24081_348218223140_8201512_n.jpg
256 ms
1554514_10207398671219172_5727884083807332225_n.jpg
296 ms
1918894_10208474318403444_3619578897624053154_n.jpg
326 ms
12063708_10153686398381248_2053574511236757172_n.jpg
328 ms
12509121_131758940538223_4722233667884505668_n.jpg
334 ms
wL6VQj7Ab77.png
74 ms
s7jcwEQH7Sx.png
88 ms
I6-MnjEovm5.js
39 ms
vlXaquuXMrr.js
42 ms
ping
74 ms
phinneywood.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
Document doesn't have a <title> element
Image elements do not have [alt] attributes
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
phinneywood.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
phinneywood.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Links do not have descriptive text
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 Phinneywood.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 Phinneywood.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.
phinneywood.com
Open Graph data is detected on the main page of Phinney Wood. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: