1.9 sec in total
231 ms
1.2 sec
418 ms
Visit proofpositive.com now to see the best up-to-date Proof Positive content for Canada and also check out these interesting facts you probably never knew about proofpositive.com
Running a Successful Business: Publishing, Writing, Photography
Visit proofpositive.comWe analyzed Proofpositive.com page load time and found that the first response time was 231 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
proofpositive.com performance score
name
value
score
weighting
Value2.6 s
64/100
10%
Value2.6 s
87/100
25%
Value5.1 s
61/100
10%
Value90 ms
98/100
30%
Value0.173
69/100
15%
Value7.9 s
44/100
10%
231 ms
90 ms
197 ms
147 ms
245 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 74% of them (46 requests) were addressed to the original Proofpositive.com, 5% (3 requests) were made to App.getresponse.com and 5% (3 requests) were made to Rcm-na.amazon-adsystem.com. The less responsive or slowest element that took the longest time to load (561 ms) belongs to the original domain Proofpositive.com.
Page size can be reduced by 356.6 kB (39%)
923.8 kB
567.2 kB
In fact, the total size of Proofpositive.com main page is 923.8 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. 45% of websites need less resources to load. Images take 484.1 kB which makes up the majority of the site volume.
Potential reduce by 55.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 55.8 kB or 81% of the original size.
Potential reduce by 19.5 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. Proof Positive images are well optimized though.
Potential reduce by 250.2 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 250.2 kB or 76% of the original size.
Potential reduce by 31.1 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. Proofpositive.com needs all CSS files to be minified and compressed as it can save up to 31.1 kB or 78% of the original size.
Number of requests can be reduced by 23 (38%)
60
37
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Proof Positive. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
proofpositive.com
231 ms
style.css
90 ms
layout.css
197 ms
custom.css
147 ms
jquery-1.2.2.pack.js
245 ms
htmltooltip.js
182 ms
widget.css
156 ms
default.min.css
180 ms
AJS.js
279 ms
AJS_fx.js
270 ms
gb_scripts.js
288 ms
gb_styles.css
287 ms
view_webform.js
67 ms
jquery.adrotate.clicktracker.js
328 ms
wp-embed.min.js
356 ms
e-201611.js
4 ms
e-201611.js
19 ms
wp-emoji-release.min.js
92 ms
dot-ddd.gif
186 ms
TheLastLine1.jpg
186 ms
TheOpeningBell1.jpg
185 ms
NeverTooSoon1.jpg
187 ms
confessions2.jpg
187 ms
LovingYourself-W1.jpg
186 ms
FOREXTrading1.jpg
187 ms
ForOne1.jpg
192 ms
DoggysFavoriteColors1.jpg
187 ms
TheGoddessWithin1.jpg
222 ms
HighwaytoDystopia2.jpg
223 ms
AureateSpectacles2.png
293 ms
The7Habits1.jpg
231 ms
DarkSky1.jpg
294 ms
MalalasMission1.jpg
261 ms
deleted.jpg
298 ms
takes-a-fool.jpg
298 ms
AuntJudy-1.jpg
312 ms
book-reviewers-banner-03.jpg
432 ms
mysterious-blood-banner2.jpg
436 ms
rainbow-dead-banner5-2.jpg
441 ms
never-too-soon.jpg
439 ms
moon-men.jpg
389 ms
wake-not-the-hangman.jpg
449 ms
dark-sky.jpg
522 ms
last-line-e1457728769678.jpg
561 ms
goats-gone-wild.jpg
504 ms
arrow.png
14 ms
cm
13 ms
cm
13 ms
cm
17 ms
VXD168-evergreenAssociateAds-benefit-assoc-300x250
11 ms
7 ms
6 ms
gc_gen_assoc-300x250.png
8 ms
5 ms
hdx89_associate_300x250.jpg
8 ms
g.gif
125 ms
webform-out.js
24 ms
w_close.gif
90 ms
header_bg.gif
88 ms
g_close.gif
88 ms
indicator.gif
89 ms
recaptcha_ajax.js
106 ms
proofpositive.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.
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
proofpositive.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
proofpositive.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Proofpositive.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 Proofpositive.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.
proofpositive.com
Open Graph description is not detected on the main page of Proof Positive. 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: