11.3 sec in total
2.1 sec
7.7 sec
1.5 sec
Visit behindbluelines.com now to see the best up-to-date Behind Blue Lines content and also check out these interesting facts you probably never knew about behindbluelines.com
Behind Blue Lines is a political, cultural and historical blog by David Crocker, an Attorney and Solicitor from Portland, Maine.
Visit behindbluelines.comWe analyzed Behindbluelines.com page load time and found that the first response time was 2.1 sec and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
behindbluelines.com performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value5.0 s
27/100
25%
Value3.7 s
85/100
10%
Value340 ms
74/100
30%
Value0
100/100
15%
Value3.5 s
92/100
10%
2105 ms
166 ms
168 ms
153 ms
156 ms
Our browser made a total of 184 requests to load all elements on the main page. We found that 19% of them (35 requests) were addressed to the original Behindbluelines.com, 18% (34 requests) were made to Apis.google.com and 14% (25 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 1.4 MB (67%)
2.1 MB
692.4 kB
In fact, the total size of Behindbluelines.com main page is 2.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. 80% 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. HTML takes 690.2 kB which makes up the majority of the site volume.
Potential reduce by 642.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 642.8 kB or 93% of the original size.
Potential reduce by 1.7 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. Behind Blue Lines images are well optimized though.
Potential reduce by 452.4 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 452.4 kB or 71% of the original size.
Potential reduce by 304.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. Behindbluelines.com needs all CSS files to be minified and compressed as it can save up to 304.8 kB or 83% of the original size.
Number of requests can be reduced by 80 (45%)
179
99
The browser has sent 179 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Behind Blue Lines. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 61 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.behindbluelines.com
2105 ms
style.css
166 ms
layout.css
168 ms
custom.css
153 ms
widget.css
156 ms
sociable.css
148 ms
twitter-feed.css
205 ms
style.css
290 ms
jetpack.css
304 ms
jquery.js
412 ms
jquery-migrate.min.js
280 ms
sociable.js
279 ms
vuible.js
289 ms
addtofavorites.js
404 ms
bubble.js
428 ms
style.css
427 ms
plusone.js
39 ms
widgets.js
5 ms
in.js
63 ms
hostedbadge.php
152 ms
hostedbadge.php
155 ms
hostedbadge.php
154 ms
hostedbadge.php
150 ms
hostedbadge.php
149 ms
hostedbadge.php
150 ms
hostedbadge.php
176 ms
hostedbadge.php
170 ms
hostedbadge.php
178 ms
hostedbadge.php
226 ms
hostedbadge.php
225 ms
hostedbadge.php
226 ms
hostedbadge.php
250 ms
hostedbadge.php
254 ms
hostedbadge.php
264 ms
hostedbadge.php
299 ms
hostedbadge.php
299 ms
hostedbadge.php
303 ms
hostedbadge.php
338 ms
hostedbadge.php
328 ms
hostedbadge.php
338 ms
hostedbadge.php
412 ms
hostedbadge.php
411 ms
hostedbadge.php
411 ms
hostedbadge.php
413 ms
AmazonWidgets.js
5 ms
devicepx-jetpack.js
4 ms
wp-embed.min.js
279 ms
e-201611.js
4 ms
wp-emoji-release.min.js
244 ms
plusone.js
95 ms
cb=gapi.loaded_0
55 ms
4.jpg
262 ms
attacked02.jpg
686 ms
Karl-Marx-9401219-1-402.jpg
270 ms
background.gif
114 ms
Banner.png
902 ms
icon-rss.gif
138 ms
dot-ddd.gif
135 ms
option1_16.png
148 ms
more.png
135 ms
closelabel.png
261 ms
rightlg.gif
608 ms
close.png
302 ms
twitter.png
258 ms
facebook.png
291 ms
rss.png
682 ms
linkedin.png
681 ms
followme_grab.gif
684 ms
secureAnonymousFramework
267 ms
widgets.js
8 ms
221 ms
cb=gapi.loaded_1
19 ms
fastbutton
72 ms
fastbutton
65 ms
fastbutton
114 ms
fastbutton
157 ms
postmessageRelay
133 ms
like.php
165 ms
like.php
547 ms
WujTPNkjSeM
530 ms
rs=AGLTcCOyEe7xIoYbKqvJH6xA3ail6lX-YA
20 ms
like.php
513 ms
like.php
516 ms
cb=gapi.loaded_0
89 ms
cb=gapi.loaded_1
88 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
486 ms
badge_su.js
494 ms
badges_su.css
516 ms
3193398744-postmessagerelay.js
436 ms
rpc:shindig_random.js
420 ms
like.php
417 ms
like.php
479 ms
like.php
552 ms
like.php
494 ms
qeKvIRsJabD.js
2221 ms
LVx-xkvaJ0b.png
2220 ms
share
389 ms
sprite_connect_v14.png
2113 ms
share
431 ms
share
416 ms
share
408 ms
share
375 ms
share
354 ms
share
330 ms
share
333 ms
share
309 ms
share
267 ms
share
229 ms
www-embed-player-vflfNyN_r.css
144 ms
www-embed-player.js
191 ms
like.php
160 ms
like.php
190 ms
like.php
151 ms
cb=gapi.loaded_0
10 ms
like.php
125 ms
badgeRound65x18.png
119 ms
like.php
130 ms
like.php
125 ms
like.php
104 ms
like.php
112 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
60 ms
ad_status.js
52 ms
like.php
121 ms
like.php
132 ms
like.php
125 ms
like.php
139 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
21 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
35 ms
like.php
127 ms
q
8 ms
8002_6.js
14 ms
like.php
1463 ms
popup.js
15 ms
nifty.js
21 ms
colors.js
19 ms
like.php
1494 ms
like.php
1489 ms
followme_top.gif
1468 ms
followme_mid.gif
1468 ms
followme_bottom.gif
1475 ms
ga.js
23 ms
g.gif
5 ms
like.php
1464 ms
__utm.gif
1410 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
987 ms
share
1020 ms
share
1003 ms
share
963 ms
share
894 ms
share
851 ms
share
802 ms
share
884 ms
share
818 ms
share
733 ms
share
664 ms
share
600 ms
share
546 ms
share
491 ms
share
425 ms
fastbutton
242 ms
fastbutton
359 ms
fastbutton
234 ms
fastbutton
234 ms
fastbutton
425 ms
fastbutton
379 ms
fastbutton
393 ms
fastbutton
399 ms
fastbutton
381 ms
fastbutton
404 ms
fastbutton
425 ms
fastbutton
549 ms
fastbutton
444 ms
fastbutton
431 ms
fastbutton
450 ms
fastbutton
483 ms
fastbutton
457 ms
fastbutton
557 ms
fastbutton
464 ms
fastbutton
541 ms
fastbutton
563 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
146 ms
ir
49 ms
49 ms
widgets.css
46 ms
behindbluelines.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
Form elements do not have associated labels
behindbluelines.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
behindbluelines.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Behindbluelines.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Behindbluelines.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.
behindbluelines.com
Open Graph data is detected on the main page of Behind Blue Lines. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: