2.4 sec in total
129 ms
2.1 sec
237 ms
Click here to check amazing PrEP Watch content for Kenya. Otherwise, check out these important facts you probably never knew about prepwatch.org
Explore data and information on PrEP across the globe. View resources by country, product, population, or topic.
Visit prepwatch.orgWe analyzed Prepwatch.org page load time and found that the first response time was 129 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
prepwatch.org performance score
name
value
score
weighting
Value2.7 s
61/100
10%
Value7.4 s
4/100
25%
Value6.2 s
43/100
10%
Value4,500 ms
0/100
30%
Value0.033
100/100
15%
Value13.0 s
12/100
10%
129 ms
38 ms
69 ms
105 ms
72 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 74% of them (34 requests) were addressed to the original Prepwatch.org, 13% (6 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (328 ms) belongs to the original domain Prepwatch.org.
Page size can be reduced by 298.8 kB (67%)
446.3 kB
147.5 kB
In fact, the total size of Prepwatch.org main page is 446.3 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. 60% of websites need less resources to load. Javascripts take 352.5 kB which makes up the majority of the site volume.
Potential reduce by 70.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 70.8 kB or 76% of the original size.
Potential reduce by 228.0 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 228.0 kB or 65% of the original size.
Number of requests can be reduced by 29 (76%)
38
9
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PrEP Watch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.prepwatch.org
129 ms
stylesheet.css
38 ms
font-awesome.min.css
69 ms
bootstrap.min.css
105 ms
prepwatch.css
72 ms
seed_wnb.css
77 ms
jquery.js
119 ms
jquery-migrate.min.js
77 ms
raphael.js
168 ms
raphael.scale.js
117 ms
map-public.compiled.js
213 ms
seed_wnb.js
116 ms
modernizr.js
138 ms
addthis_widget.js
11 ms
jquery.js
182 ms
fastclick.js
136 ms
foundation.min.js
181 ms
bootstrap.min.js
179 ms
jquery.easing.min.js
11 ms
qppr_frontend_script.min.js
180 ms
modernizr.custom.88940.js
196 ms
matchMedia.js
198 ms
matchMedia.addListener.js
199 ms
enquire.min.js
203 ms
jquery.matchHeight-min.js
204 ms
jquery.fitvids.js
327 ms
site.js
328 ms
prep-answers.js
327 ms
css
25 ms
css
16 ms
wp-emoji-release.min.js
210 ms
avac-logo-sm.png
106 ms
prepwatch-logo-lg.png
109 ms
prep-in-the-bg.png
110 ms
navy-bullet.png
109 ms
mail-blue.png
111 ms
avac-logo.png
109 ms
9k-RPmcnxYEPm8CNFsH2gg.woff
70 ms
wkfQbvfT_02e2IWO3yYueQ.woff
70 ms
JbtMzqLaYbbbCL9X6EvaIxsxEYwM7FgeyaSgU71cLG0.woff
70 ms
1ImRNPx4870-D9a1EBUdPBsxEYwM7FgeyaSgU71cLG0.woff
71 ms
IczWvq5y_Cwwv_rBjOtT0w.woff
70 ms
oUan5VrEkpzIazlUe5ieaA.woff
71 ms
fontawesome-webfont.woff
73 ms
300lo.json
36 ms
sh.8e5f85691f9aaa082472a194.html
15 ms
prepwatch.org 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
Form elements do not have associated labels
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>).
prepwatch.org 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
prepwatch.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
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 Prepwatch.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 Prepwatch.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.
prepwatch.org
Open Graph data is detected on the main page of PrEP Watch. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: