2.1 sec in total
95 ms
1.9 sec
168 ms
Visit plannedparenthood.org now to see the best up-to-date Planned Parenthood content for United States and also check out these interesting facts you probably never knew about plannedparenthood.org
Visit plannedparenthood.orgWe analyzed Plannedparenthood.org page load time and found that the first response time was 95 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
plannedparenthood.org performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value6.0 s
13/100
25%
Value6.0 s
46/100
10%
Value6,540 ms
0/100
30%
Value0.108
88/100
15%
Value22.5 s
1/100
10%
95 ms
134 ms
156 ms
19 ms
47 ms
Our browser made a total of 142 requests to load all elements on the main page. We found that 40% of them (57 requests) were addressed to the original Plannedparenthood.org, 7% (10 requests) were made to Google-analytics.com and 4% (6 requests) were made to Fast.fonts.net. The less responsive or slowest element that took the longest time to load (728 ms) relates to the external source Cs.gssprt.jp.
Page size can be reduced by 744.0 kB (71%)
1.1 MB
308.5 kB
In fact, the total size of Plannedparenthood.org main page is 1.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. 55% of websites need less resources to load. CSS take 475.4 kB which makes up the majority of the site volume.
Potential reduce by 93.1 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 93.1 kB or 80% of the original size.
Potential reduce by 78.0 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. Obviously, Planned Parenthood needs image optimization as it can save up to 78.0 kB or 50% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 145.7 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 145.7 kB or 48% of the original size.
Potential reduce by 427.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. Plannedparenthood.org needs all CSS files to be minified and compressed as it can save up to 427.1 kB or 90% of the original size.
Number of requests can be reduced by 101 (77%)
131
30
The browser has sent 131 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Planned Parenthood. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.plannedparenthood.org
95 ms
5e9f5a2f-7e43-4ba8-b08d-fa31beabf427.css
134 ms
styles.css
156 ms
ipad-landscape.css
19 ms
foundation_tables.css
47 ms
to_be_merged.css
19 ms
ccm.base.css
64 ms
jquery.js
46 ms
ccm.base.js
23 ms
lean-slider.js
22 ms
lpChatV3.min.js
44 ms
chat_promo.js
26 ms
detectmobilebrowser.js
49 ms
modernizr.custom.js
47 ms
lean-slider.js
46 ms
respond.js
51 ms
bootstrap.min.js
50 ms
bootstrap-paginator.min.js
53 ms
jquery.sidr.min.js
51 ms
detectmobilebrowser.js
59 ms
markup.min.js
59 ms
arrays.js
77 ms
jquery.cookie.js
66 ms
jquery.scrolldepth.min.js
61 ms
detectmobilebrowser.js
63 ms
promos.js
60 ms
alt_nav.js
64 ms
proofpilot.js
66 ms
buttons.js
107 ms
typography.css
73 ms
lpChatV3.min.js
72 ms
jquery.pageslide.min.js
71 ms
foundation.pageslide.js
72 ms
waypoints.min.js
78 ms
waypoints-sticky.min.js
78 ms
magnific.popup.min.js
84 ms
fastclick.js
75 ms
main.js
80 ms
iphone.css
87 ms
gtm.js
138 ms
diagonal.png
43 ms
header_bg.png
36 ms
logo_lockup.png
44 ms
header_bg_right.jpg
36 ms
take_action_donate_2010.gif
35 ms
desktop_arrows_sprite.png
34 ms
alt-arrows-sprite.png
41 ms
a02b8363413e1fdf8a86a8ecc5ddb612_f11060.jpg
41 ms
planned-parenthood-person-speech-bubble-icon-130x130.png
40 ms
3e0bb57d10080daaa560aaadbb04aaad_f1259.jpg
40 ms
08fc6add2c56a042da9a5c31712cf2a3_f5703.jpg
52 ms
6f06aa9dbc0ef702f78f1e25765a8334_f1309.png
51 ms
9b581d294f97e1f8444c42dfb7c3e74b_f1508.jpg
46 ms
planned-parenthood-share-on-twitter.png
46 ms
planned-parenthood-share-on-facebook.png
60 ms
planned-parenthood-share-on-tumblr.png
50 ms
planned-parenthood-share-on-google.png
60 ms
planned-parenthood-share-on-pinterest.png
60 ms
gtm.js
92 ms
842088d0-1ae2-40d0-8561-3c95761ba7a6.woff
136 ms
102ab74c-0e84-4fe5-a17a-b20fb643591a.woff
182 ms
pictonic.ttf
28 ms
42aacb2f-222e-46f5-a95a-1c22948ee0d1.woff
241 ms
aef05e22-e1d4-4e59-bc2e-a71c13c26cca.woff
263 ms
quant.js
127 ms
activityi;src=4558437;type=plann0;cat=ppfahome;ord=1318051721900.7014
156 ms
tc.min.js
250 ms
530dee22-e3c1-4e9f-bf62-c31d510d9656.woff
197 ms
ipad-portrait.css
106 ms
baseURI.lpCsds
231 ms
getAllAppDefault.esi
184 ms
analytics.js
170 ms
activity;src=4796901;type=track0;cat=htvkc0;ord=1;num=198487160052
165 ms
iframe_api
165 ms
activity;src=5289002;type=ip16101;cat=plann0;ord=5862196255941
151 ms
iframe
144 ms
pixel;r=655825141;a=p-f83mnHGect3fW;labels=_fp.event.Homepage;fpan=1;fpa=P0-362807292-1456750077864;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456750077864;tzo=-180;ref=;url=https%3A%2F%2Fwww.plannedparenthood.org%2F;ogl=title.Planned%20Parenthood%20%7C%20Official%20Site%2Cdescription.Planned%20Parenthood%20%7C%20Official%20Site%2Cimage.https%3A%2F%2Fwww%252Eplannedparenthood%252Eorg%2Fimages%2Fplanned_parenthood_sharing_small%252Epng
140 ms
getSegment.php
449 ms
iframe
56 ms
collect
23 ms
collect
98 ms
www-widgetapi.js
54 ms
collect
102 ms
collect
124 ms
collect
232 ms
collect
20 ms
collect
32 ms
collect
32 ms
postmessage.min.html
134 ms
pixel
42 ms
cm
54 ms
Pug
236 ms
cx
247 ms
adb.gif
196 ms
1
216 ms
cs
728 ms
sync
194 ms
13583483.json
136 ms
cm
122 ms
availability.json
31 ms
360947.gif
31 ms
sd
30 ms
demconf.jpg
30 ms
cx
93 ms
generic
99 ms
lr.gif
101 ms
xrefid.xgi
57 ms
cm
49 ms
93 ms
mapuid
118 ms
362378.gif
39 ms
rum
65 ms
cx
28 ms
t.dhj
90 ms
21 ms
pixel
45 ms
xrefid.xgi
30 ms
13 ms
match
7 ms
t.dhj
26 ms
pixel.gif
55 ms
tap.php
125 ms
s-3271.xgi
42 ms
hbpix
103 ms
cm
18 ms
xrefid.xgi
7 ms
8 ms
10 ms
img;m=11022203137504;cache=
109 ms
nr-885.min.js
51 ms
chartbeat.js
97 ms
collect
17 ms
collect
4 ms
collect
5 ms
collect
5 ms
collect
5 ms
afa06086e4
115 ms
ping
25 ms
index.html
43 ms
buttons-secure.css
59 ms
stcommon.2b05accc08f1ee42fe1983647ab923ea.js
80 ms
st.1188278743c14064d5e8ae56c8ada29c.js
50 ms
plannedparenthood.org 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-hidden="true"] elements contain focusable descendents
ARIA IDs are not unique
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
No form fields have multiple labels
Form elements do not have associated labels
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
plannedparenthood.org 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
plannedparenthood.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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 Plannedparenthood.org 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 Plannedparenthood.org 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.
plannedparenthood.org
Open Graph data is detected on the main page of Planned Parenthood. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: