Access worldobesitydata.org. World Obesity Federation Global Obesity Observatory

worldobesitydata.org screenshot

40

Performance

Renders faster than
59% of other websites
78

Accessibility

Visual factors better than
that of 45% of websites
92

Best Practices

More advanced features
available than in
80% of websites
90

SEO

Google-friendlier than
68% of websites

First Response

45 ms

Resources Loaded

4.6 sec

Page Rendered

82 ms

worldobesitydata.org screenshot

About Website

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.org

Key Findings

We analyzed Worldobesitydata.org page load time and found that the first response time was 45 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

72/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value19,360 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value46.7 s

0/100

10%

worldobesitydata.org

45 ms

data.worldobesity.org

207 ms

data.worldobesity.org

505 ms

css2

40 ms

wod.max.css

181 ms

Our browser made a total of 244 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Worldobesitydata.org, 98% (238 requests) were made to Data.worldobesity.org and 0% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (967 ms) relates to the external source Data.worldobesity.org.

Content Size

4.1 MB

After Optimization

1.3 MB

In fact, the total size of Worldobesitydata.org main page is 4.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. Javascripts take 3.9 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 175.5 kB

Original 205.9 kB
After minification 205.9 kB
After compression 30.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. 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 175.5 kB or 85% of the original size.

JavaScript Optimization

-67%

Potential reduce by 2.6 MB

Original 3.9 MB
After minification 3.8 MB
After compression 1.3 MB

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 2.6 MB or 67% of the original size.

CSS Optimization

-7%

Potential reduce by 966 B

Original 14.6 kB
After minification 14.6 kB
After compression 13.6 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. Worldobesitydata.org has all CSS files already compressed.

Requests Now

240

After Optimization

140

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.

Accessibility Issues

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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.

High

Form elements do not have associated labels

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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/).

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

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.

Social Sharing Optimization

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: