4.4 sec in total
15 ms
4.3 sec
113 ms
Welcome to worldobesitydata.org homepage info - get ready to check World Obesity Data best content right away, or after learning these important things about worldobesitydata.org
At the World Obesity Federation we have been collating data for over 20 years. This database is online and available to view in various formats.
Visit worldobesitydata.orgWe analyzed Worldobesitydata.org page load time and found that the first response time was 15 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
worldobesitydata.org performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value3.1 s
75/100
25%
Value5.1 s
61/100
10%
Value15,240 ms
0/100
30%
Value0
100/100
15%
Value29.7 s
0/100
10%
15 ms
170 ms
469 ms
36 ms
160 ms
Our browser made a total of 246 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Worldobesitydata.org, 97% (238 requests) were made to Data.worldobesity.org and 1% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (850 ms) relates to the external source Data.worldobesity.org.
Page size can be reduced by 183.6 kB (12%)
1.5 MB
1.3 MB
In fact, the total size of Worldobesitydata.org main page is 1.5 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. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 174.2 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 174.2 kB or 85% of the original size.
Potential reduce by 8.5 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.
Potential reduce by 964 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. Worldobesitydata.org has all CSS files already compressed.
Number of requests can be reduced by 99 (41%)
240
141
The browser has sent 240 CSS, Javascripts, AJAX and image requests in order to completely render the main page of World Obesity Data. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
worldobesitydata.org
15 ms
data.worldobesity.org
170 ms
data.worldobesity.org
469 ms
css2
36 ms
wod.max.css
160 ms
plotly-latest.min.js
850 ms
js
55 ms
mootools.js
314 ms
api.js
204 ms
world-obesity.svg
158 ms
GB.svg
209 ms
BG.svg
218 ms
HR.svg
286 ms
CZ.svg
287 ms
DK.svg
289 ms
NL.svg
297 ms
EE.svg
301 ms
FI.svg
364 ms
FR.svg
366 ms
DE.svg
368 ms
GR.svg
380 ms
HU.svg
383 ms
IE.svg
445 ms
IT.svg
446 ms
LV.svg
446 ms
LT.svg
462 ms
MT.svg
465 ms
PL.svg
525 ms
PT.svg
527 ms
RO.svg
526 ms
SK.svg
547 ms
SI.svg
549 ms
ES.svg
828 ms
SE.svg
826 ms
cur.svg
830 ms
AF.svg
831 ms
AL.svg
833 ms
DZ.svg
835 ms
AS.svg
837 ms
AD.svg
838 ms
AO.svg
840 ms
AI.svg
842 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GCC5ntA.ttf
67 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GMS5ntA.ttf
90 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4G1ilntA.ttf
91 ms
AG.svg
843 ms
recaptcha__en.js
56 ms
AR.svg
691 ms
AM.svg
664 ms
cmsplus_frontend.js
646 ms
AW.svg
636 ms
AU.svg
569 ms
AT.svg
571 ms
AZ.svg
585 ms
PT-20.svg
579 ms
BS.svg
578 ms
BH.svg
515 ms
BD.svg
526 ms
BB.svg
524 ms
BY.svg
541 ms
BE.svg
540 ms
BZ.svg
481 ms
BJ.svg
478 ms
BM.svg
517 ms
BT.svg
504 ms
BO.svg
535 ms
BA.svg
477 ms
BW.svg
478 ms
BR.svg
480 ms
VG.svg
500 ms
BN.svg
501 ms
BF.svg
250 ms
BI.svg
254 ms
CV.svg
251 ms
KH.svg
253 ms
CM.svg
296 ms
CA.svg
296 ms
KY.svg
320 ms
CF.svg
321 ms
TD.svg
320 ms
CL.svg
320 ms
CN.svg
368 ms
CO.svg
368 ms
KM.svg
387 ms
CG.svg
387 ms
CK.svg
389 ms
CR.svg
389 ms
CI.svg
440 ms
CU.svg
428 ms
CY.svg
441 ms
CD.svg
440 ms
DJ.svg
441 ms
DM.svg
430 ms
DO.svg
486 ms
EC.svg
488 ms
EG.svg
474 ms
SV.svg
471 ms
GB-ENG.svg
471 ms
GQ.svg
472 ms
wod.max.js
585 ms
ER.svg
498 ms
SZ.svg
473 ms
ET.svg
471 ms
FM.svg
471 ms
FJ.svg
472 ms
GF.svg
500 ms
PF.svg
512 ms
GA.svg
484 ms
GM.svg
481 ms
GE.svg
483 ms
GH.svg
548 ms
GI.svg
507 ms
GL.svg
498 ms
GD.svg
475 ms
GP.svg
474 ms
GU.svg
474 ms
GT.svg
546 ms
GN.svg
503 ms
GW.svg
497 ms
GY.svg
477 ms
HT.svg
475 ms
HN.svg
477 ms
HK.svg
546 ms
IS.svg
494 ms
IN.svg
493 ms
ID.svg
478 ms
IR.svg
481 ms
IQ.svg
481 ms
IL.svg
550 ms
JM.svg
491 ms
JP.svg
491 ms
JO.svg
481 ms
KZ.svg
486 ms
KE.svg
485 ms
KI.svg
550 ms
XK.svg
488 ms
KW.svg
478 ms
KG.svg
479 ms
LA.svg
485 ms
LB.svg
487 ms
LS.svg
479 ms
LR.svg
468 ms
LY.svg
467 ms
LI.svg
468 ms
LU.svg
483 ms
MG.svg
485 ms
MW.svg
475 ms
MY.svg
475 ms
MV.svg
475 ms
ML.svg
474 ms
MH.svg
491 ms
MQ.svg
493 ms
MR.svg
478 ms
MU.svg
475 ms
MX.svg
470 ms
MD.svg
474 ms
MC.svg
494 ms
MN.svg
495 ms
ME.svg
478 ms
MS.svg
478 ms
MA.svg
474 ms
MZ.svg
477 ms
MM.svg
501 ms
NA.svg
497 ms
NR.svg
484 ms
NP.svg
482 ms
NC.svg
470 ms
NZ.svg
483 ms
NI.svg
500 ms
NE.svg
500 ms
NG.svg
476 ms
NU.svg
474 ms
KP.svg
469 ms
MK.svg
474 ms
GB-NIR.svg
503 ms
MP.svg
500 ms
NO.svg
477 ms
OM.svg
475 ms
PK.svg
475 ms
PW.svg
477 ms
PS.svg
500 ms
PA.svg
500 ms
PG.svg
478 ms
PY.svg
477 ms
PE.svg
471 ms
PH.svg
477 ms
PR.svg
500 ms
QA.svg
501 ms
RE.svg
474 ms
RU.svg
476 ms
RW.svg
477 ms
KN.svg
477 ms
LC.svg
502 ms
VC.svg
500 ms
WS.svg
474 ms
SM.svg
476 ms
ST.svg
473 ms
SA.svg
477 ms
GB-SCT.svg
500 ms
SN.svg
502 ms
RS.svg
467 ms
SC.svg
467 ms
SL.svg
468 ms
SG.svg
468 ms
SB.svg
499 ms
SO.svg
500 ms
ZA.svg
473 ms
KR.svg
474 ms
SS.svg
473 ms
LK.svg
475 ms
SH.svg
508 ms
SD.svg
494 ms
SR.svg
476 ms
CH.svg
478 ms
SY.svg
476 ms
TW.svg
477 ms
TJ.svg
501 ms
TZ.svg
506 ms
TH.svg
475 ms
TL.svg
472 ms
TG.svg
471 ms
TK.svg
472 ms
TO.svg
499 ms
TT.svg
508 ms
TN.svg
471 ms
TR.svg
471 ms
TM.svg
472 ms
TC.svg
472 ms
TV.svg
502 ms
UG.svg
497 ms
UA.svg
473 ms
AE.svg
472 ms
US.svg
476 ms
UY.svg
477 ms
UZ.svg
493 ms
VU.svg
495 ms
VE.svg
475 ms
VN.svg
477 ms
GB-WLS.svg
475 ms
WF.svg
478 ms
EH.svg
490 ms
YE.svg
491 ms
ZM.svg
475 ms
ZW.svg
476 ms
fl_loading.svg
479 ms
flag-europe.svg
484 ms
worldobesitydata.org accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
worldobesitydata.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
Missing source maps for large first-party JavaScript
worldobesitydata.org 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 doesn't use 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 Worldobesitydata.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 Worldobesitydata.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.
worldobesitydata.org
Open Graph description is not detected on the main page of World Obesity Data. 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: