2.8 sec in total
381 ms
2.3 sec
87 ms
Welcome to watog.org homepage info - get ready to check WATOG best content right away, or after learning these important things about watog.org
WORLD ASSOCIATION FOR TRAINEES IN OBSTETRICS AND GYNECOLOGY WATOG
Visit watog.orgWe analyzed Watog.org page load time and found that the first response time was 381 ms and then it took 2.4 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.
watog.org performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value0
0/100
25%
Value11.8 s
4/100
10%
Value2,190 ms
6/100
30%
Value0.01
100/100
15%
Value21.8 s
1/100
10%
381 ms
1344 ms
46 ms
54 ms
49 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Watog.org, 49% (23 requests) were made to Static.parastorage.com and 21% (10 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Executive006.wixsite.com.
Page size can be reduced by 3.5 kB (1%)
379.3 kB
375.7 kB
In fact, the total size of Watog.org main page is 379.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. 55% of websites need less resources to load. Javascripts take 248.7 kB which makes up the majority of the site volume.
Potential reduce by 600 B
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 600 B or 56% of the original size.
Potential reduce by 87 B
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. WATOG images are well optimized though.
Potential reduce by 2.8 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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 15 (56%)
27
12
The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WATOG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
watog.org
381 ms
watog
1344 ms
originTrials.41d7301a.bundle.min.js
46 ms
minified.js
54 ms
focus-within-polyfill.js
49 ms
polyfill.min.js
38 ms
5402.chunk.min.js
30 ms
2013.chunk.min.js
29 ms
5141.chunk.min.js
31 ms
SingleEvent.chunk.min.js
260 ms
thunderbolt-commons.24e46262.bundle.min.js
219 ms
main.8752ee81.bundle.min.js
247 ms
lodash.min.js
246 ms
react.production.min.js
220 ms
react-dom.production.min.js
226 ms
siteTags.bundle.min.js
247 ms
wix-perf-measure.umd.min.js
248 ms
WATOG-LOGO-1_edited.png
322 ms
bundle.min.js
169 ms
WATOG-LOGO-1_edited.png
278 ms
966ae3_56f507d3aac54c8badc4968d8b8a8fac~mv2.png
282 ms
966ae3_7ecbc64aedde4325bd41486e38a36dc8~mv2.jpg
359 ms
966ae3_8f7a50e1ca5445c9ac6595ef5e8f5800~mv2.jpg
276 ms
966ae3_bc2b2eae3b5e4c9abc7b115ec7d47aed~mv2.png
288 ms
file.woff
278 ms
file.woff
196 ms
file.woff
195 ms
60be5c39-863e-40cb-9434-6ebafb62ab2b.woff
21 ms
5b4a262e-3342-44e2-8ad7-719998a68134.woff
27 ms
5b29e833-1b7a-40ab-82a5-cfd69c8650f4.woff
26 ms
175 ms
166 ms
159 ms
164 ms
177 ms
172 ms
193 ms
209 ms
208 ms
202 ms
deprecation-en.v5.html
5 ms
bolt-performance
27 ms
deprecation-style.v5.css
9 ms
right-arrow.svg
9 ms
WixMadeforDisplay_W_Bd.woff
5 ms
WixMadeforText_W_Bd.woff
6 ms
WixMadeforText_W_Rg.woff
6 ms
watog.org accessibility score
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
watog.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
Page has valid source maps
watog.org SEO score
EN
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Watog.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Watog.org main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
watog.org
Open Graph description is not detected on the main page of WATOG. 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: