22.8 sec in total
260 ms
21.8 sec
784 ms
Welcome to wendypowell.ca homepage info - get ready to check Wendy Powell best content right away, or after learning these important things about wendypowell.ca
You have found a huge amount of information about living well, dealing with a narcissist and my love of walking. Browse through hundreds of blogs and most importantly, enjoy your stay. Wendy
Visit wendypowell.caWe analyzed Wendypowell.ca page load time and found that the first response time was 260 ms and then it took 22.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% 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.
wendypowell.ca performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value12.1 s
0/100
25%
Value37.9 s
0/100
10%
Value54,730 ms
0/100
30%
Value0.022
100/100
15%
Value77.3 s
0/100
10%
260 ms
103 ms
155 ms
130 ms
154 ms
Our browser made a total of 225 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Wendypowell.ca, 10% (22 requests) were made to S.pubmine.com and 6% (14 requests) were made to S0.wp.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Ssl-market-east.smrtb.com.
Page size can be reduced by 469.7 kB (5%)
8.9 MB
8.4 MB
In fact, the total size of Wendypowell.ca main page is 8.9 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. 60% of websites need less resources to load. Images take 8.6 MB which makes up the majority of the site volume.
Potential reduce by 73.3 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 73.3 kB or 78% of the original size.
Potential reduce by 322.1 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. Wendy Powell images are well optimized though.
Potential reduce by 74.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 74.2 kB or 40% of the original size.
Potential reduce by 178 B
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. Wendypowell.ca has all CSS files already compressed.
Number of requests can be reduced by 156 (78%)
199
43
The browser has sent 199 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wendy Powell. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
wendyjpowell.wordpress.com
260 ms
wp-emoji-release.min.js
103 ms
155 ms
130 ms
css
154 ms
css
196 ms
css
214 ms
138 ms
130 ms
187 ms
gprofiles.js
183 ms
wpgroho.js
126 ms
134 ms
147 ms
w.js
183 ms
global-print.css
19 ms
conf
263 ms
img_0053.jpg
543 ms
red-medium.png
12 ms
87e22245aa6fb849ddbcac837e2aa1ad
146 ms
the_narcissist_survi-csp_proof-12-02-13.jpg
262 ms
img_0363.jpg
309 ms
img_0218.jpg
4621 ms
img_5047.jpg
324 ms
img_5775.jpg
521 ms
envelope.jpg
321 ms
img_5058.jpg
2270 ms
edincon.woff
59 ms
platform.js
179 ms
master.html
141 ms
g.gif
149 ms
hovercard.min.css
58 ms
services.min.css
98 ms
g.gif
162 ms
g.gif
141 ms
rlt-proxy.js
36 ms
34 ms
index.html
30 ms
jquery.js
35 ms
89 ms
ata.js
89 ms
postmessage.js
15 ms
jed.js
15 ms
underscore.min.js
16 ms
g.gif
34 ms
5.js
124 ms
pixel
125 ms
tag.js
567 ms
uc.html
562 ms
user_sync.html
659 ms
user_sync.html
654 ms
prbds2s
815 ms
async_usersync.html
1360 ms
user_sync.html
642 ms
usync.html
1347 ms
checksync.php
1347 ms
iframe
617 ms
jquery.wpcom-proxy-request.js
333 ms
jslog
312 ms
match
455 ms
match
805 ms
397 ms
follow-rest.js
388 ms
all
20007 ms
30907
2466 ms
setuid
1830 ms
match
1548 ms
sync
684 ms
jslog
641 ms
PugMaster
2377 ms
user_sync.html
1118 ms
match
621 ms
usermatch
1737 ms
us.gif
2492 ms
2938 ms
match
1247 ms
2970 ms
match
1222 ms
usersync.aspx
2623 ms
usync.js
1045 ms
pd
1178 ms
match
1034 ms
match
1023 ms
match
1016 ms
usersync
2492 ms
getuid
1822 ms
engine
2279 ms
0.gif
1986 ms
match
546 ms
match
923 ms
match
892 ms
cksync.php
850 ms
cs
2723 ms
match
776 ms
ibs:dpid=23728&dpuuid=Y0ITWz6TYBRy66o2C12J9AAA%26572
428 ms
getuid
1104 ms
us.gif
1321 ms
40cf76d5-f269-ea55-cba8-625dcb7d20b7
1023 ms
match
769 ms
demconf.jpg
1002 ms
pixel
1560 ms
usersync
2414 ms
us.gif
1335 ms
cksync.php
1271 ms
us.gif
1471 ms
us.gif
1473 ms
info2
1009 ms
usersync
2628 ms
us.gif
1360 ms
us.gif
1682 ms
usersync
2520 ms
pubmatic
2806 ms
3D1F7CE5-FE0A-4C96-B3CD-96741F5FC880
1085 ms
pixel
2214 ms
pixel
2216 ms
usersync
2407 ms
us.gif
1563 ms
usersync
2455 ms
usersync
2408 ms
usync.html
842 ms
rum
2227 ms
tap.php
683 ms
usersync
2291 ms
us.gif
1081 ms
usync.html
1653 ms
cksync.php
1081 ms
cksync.php
1685 ms
sync
1075 ms
cksync.html
2145 ms
PugMaster
669 ms
PugMaster
1698 ms
usersync
1967 ms
usersync
1962 ms
pixel
1498 ms
usg.gif
1486 ms
pixel
1775 ms
sd
1220 ms
usersync
1929 ms
cksync
1736 ms
b9pj45k4
1105 ms
Pug
1991 ms
1000.gif
1326 ms
usersync
1788 ms
match
1304 ms
rtset
1272 ms
user_sync.html
1206 ms
Pug
1842 ms
usersync
1663 ms
match
1371 ms
match
1081 ms
usersync
1426 ms
usersync
1394 ms
usersync
1361 ms
usync.html
1107 ms
cksync.php
1283 ms
PugMaster
820 ms
usermatchredir
800 ms
Pug
1511 ms
cs&eq_cc=1
618 ms
Pug
1438 ms
cksync.php
730 ms
pixel
596 ms
sd
592 ms
pixel
597 ms
dcm
595 ms
tap.php
712 ms
cksync
608 ms
dcm
491 ms
usersync
902 ms
usersync
902 ms
sd
484 ms
info
435 ms
g.pixel
1189 ms
usersync.aspx
413 ms
match
400 ms
cksync.php
838 ms
match
348 ms
sd
641 ms
Pug
1111 ms
sn.ashx
1637 ms
i.match
1362 ms
usersync
596 ms
crum
581 ms
match
1127 ms
match
1083 ms
tap.php
540 ms
cksync.php
679 ms
match
916 ms
Pug
805 ms
crum
872 ms
Pug
729 ms
Pug
958 ms
Pug
949 ms
match
1161 ms
Pug
718 ms
Pug
594 ms
match
1085 ms
usersync
564 ms
crum
698 ms
getuid
561 ms
cksync.php
444 ms
match
701 ms
ecm3
485 ms
Pug
382 ms
Pug
405 ms
usersync
347 ms
ecm3
345 ms
usersync
330 ms
Pug
327 ms
Artemis
409 ms
Pug
276 ms
i.match
454 ms
match
229 ms
Pug
230 ms
qmap
281 ms
temp.com
189 ms
Pug
164 ms
Pug
150 ms
pbmtc.gif
97 ms
Pug
72 ms
match
61 ms
generic
59 ms
receive
28 ms
actionbar.css
3 ms
actionbar.js
12 ms
wendypowell.ca 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
wendypowell.ca 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
Browser errors were logged to the console
wendypowell.ca SEO score
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 Wendypowell.ca 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 Wendypowell.ca 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.
wendypowell.ca
Open Graph data is detected on the main page of Wendy Powell. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: