13.5 sec in total
347 ms
12 sec
1.2 sec
Visit compassplaybook.com now to see the best up-to-date Com Passplaybook content for United States and also check out these interesting facts you probably never knew about compassplaybook.com
Follow Terry Pappy and explore their bibliography from Amazon.com's Terry Pappy Author Page.
Visit compassplaybook.comWe analyzed Compassplaybook.com page load time and found that the first response time was 347 ms and then it took 13.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
compassplaybook.com performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value3.0 s
78/100
25%
Value4.8 s
67/100
10%
Value330 ms
75/100
30%
Value0.009
100/100
15%
Value7.8 s
44/100
10%
347 ms
85 ms
441 ms
774 ms
436 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Compassplaybook.com, 22% (11 requests) were made to Static1.squarespace.com and 16% (8 requests) were made to Static.squarespace.com. The less responsive or slowest element that took the longest time to load (6.6 sec) relates to the external source Reddit.com.
Page size can be reduced by 997.0 kB (56%)
1.8 MB
768.4 kB
In fact, the total size of Compassplaybook.com main page is 1.8 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 1.0 MB which makes up the majority of the site volume.
Potential reduce by 189.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. 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 189.5 kB or 78% of the original size.
Potential reduce by 28.6 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. Com Passplaybook images are well optimized though.
Potential reduce by 674.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 674.9 kB or 67% of the original size.
Potential reduce by 104.0 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. Compassplaybook.com needs all CSS files to be minified and compressed as it can save up to 104.0 kB or 89% of the original size.
Number of requests can be reduced by 18 (44%)
41
23
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Com Passplaybook. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.compassplaybook.com
347 ms
css
85 ms
addthis_widget.js
441 ms
774 ms
common-ed8771b6a3d84eb7699e-min.js
436 ms
commerce-82e01d4950516749b43e-min.js
307 ms
commerce-7f4130fee43d9b486ac93410db2112d3-min.css
167 ms
site.css
2070 ms
ga.js
233 ms
play-button.png
182 ms
156 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
579 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
579 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
580 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
583 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
581 ms
PRmiXeptR36kaC0GEAetxi8cqLH4MEiSE0ROcU-qHOA.ttf
582 ms
PRmiXeptR36kaC0GEAetxp_TkvowlIOtbR7ePgFOpF4.ttf
582 ms
__utm.gif
538 ms
RecordHit
622 ms
Terry+Pappy
237 ms
count.js
156 ms
blogtalkradio-logo.png
143 ms
janelStewart.jpg
205 ms
mindPeople.png
919 ms
496 ms
329 ms
203 ms
CP2014FullLogoNeg40Percent.png
141 ms
99638721
504 ms
audio-player-76e4bfcc3f9830beb388bae2002fbe6c-min.css
72 ms
audio-player-2fab571e2898e015b092-min.js
107 ms
300lo.json
190 ms
sh.953eb77977227bfd253ee158.html
168 ms
audio-player-play.png
77 ms
pinterest-062fd4ff3e3c28500f48-min.js
82 ms
layers.34f2ad207a6dc0c4eb95.js
232 ms
player.js
611 ms
player.css
502 ms
ga.js
463 ms
vuid.min.js
541 ms
fql
150 ms
count.json
111 ms
info.json
6630 ms
shares.json
133 ms
__utm.gif
60 ms
proxy.html
141 ms
480879107.jpg
626 ms
9934019_60x60.jpg
210 ms
compassplaybook.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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
[role]s do not have all required [aria-*] attributes
[role]s are not contained by their required parent element
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
compassplaybook.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
compassplaybook.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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Compassplaybook.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 Compassplaybook.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.
compassplaybook.com
Open Graph description is not detected on the main page of Com Passplaybook. 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: