1.2 sec in total
84 ms
705 ms
440 ms
Click here to check amazing Propecia content. Otherwise, check out these important facts you probably never knew about propecia.com
Our health solutions, biosimilars and established brands are helping women to live better, healthier lives.
Visit propecia.comWe analyzed Propecia.com page load time and found that the first response time was 84 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
propecia.com performance score
name
value
score
weighting
Value1.8 s
89/100
10%
Value2.1 s
96/100
25%
Value2.9 s
95/100
10%
Value320 ms
76/100
30%
Value0.295
40/100
15%
Value5.5 s
71/100
10%
84 ms
44 ms
67 ms
77 ms
74 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Propecia.com, 88% (38 requests) were made to Organon.com and 5% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (251 ms) relates to the external source Googletagmanager.com.
Page size can be reduced by 446.5 kB (81%)
554.0 kB
107.5 kB
In fact, the total size of Propecia.com main page is 554.0 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. HTML takes 497.0 kB which makes up the majority of the site volume.
Potential reduce by 445.4 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. This page needs HTML code to be minified as it can gain 139.9 kB, which is 28% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 445.4 kB or 90% of the original size.
Potential reduce by 139 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 971 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. Propecia.com has all CSS files already compressed.
Number of requests can be reduced by 37 (90%)
41
4
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Propecia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
propecia.com
84 ms
44 ms
product-list-page.min.css
67 ms
style.min.css
77 ms
mediaelementplayer-legacy.min.css
74 ms
wp-mediaelement.min.css
75 ms
related-posts-block-styles.min.css
75 ms
classic-themes.min.css
75 ms
style.css
132 ms
style.min.css
142 ms
default-font-rtl.min.css
140 ms
otSDKStub.js
43 ms
style.css
138 ms
style.css
181 ms
tinyslider.css
182 ms
related-content-section.min.css
194 ms
image-cdn.js
208 ms
scripts.min.js
208 ms
tinyslider.js
208 ms
index.js
210 ms
gtm.js
81 ms
organon-logo.svg
26 ms
search.svg
128 ms
burger.svg
129 ms
arrow-left.svg
129 ms
arrow-down.svg
130 ms
arrow-right.svg
130 ms
arrow-right-line.svg
131 ms
css-vars-ponyfill@2
48 ms
gtm.js
251 ms
product-list-page.min.css
5 ms
style.min.css
6 ms
mediaelementplayer-legacy.min.css
7 ms
wp-mediaelement.min.css
7 ms
related-posts-block-styles.min.css
8 ms
classic-themes.min.css
9 ms
style.css
8 ms
style.min.css
10 ms
default-font-rtl.min.css
13 ms
style.css
14 ms
style.css
15 ms
tinyslider.css
15 ms
related-content-section.min.css
16 ms
propecia.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-hidden="true"] elements contain focusable descendents
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
propecia.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
Browser errors were logged to the console
propecia.com SEO score
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Propecia.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 Propecia.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.
propecia.com
Open Graph data is detected on the main page of Propecia. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: