Tools & Wizards About Us
worlddata.ai screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

worlddata.ai

Emerging Tech Services | Predictability Models Powered by WorldData.AI

Page Load Speed

2.3 sec in total

First Response

230 ms

Resources Loaded

1.6 sec

Page Rendered

467 ms

worlddata.ai screenshot

About Website

Visit worlddata.ai now to see the best up-to-date World Data content and also check out these interesting facts you probably never knew about worlddata.ai

WorldData.AI provides access to curated data from all leading public sources globally. We integrate over 8000 leading sources covering 3.3 Billion Datasets, News, and Geo Intelligence.

Visit worlddata.ai

Key Findings

We analyzed Worlddata.ai page load time and found that the first response time was 230 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

worlddata.ai performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value1,450 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

worlddata.ai

230 ms

worlddata.ai

423 ms

5626831.js

73 ms

gtm.js

98 ms

bootstrap.min.css

160 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 78% of them (50 requests) were addressed to the original Worlddata.ai, 9% (6 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (680 ms) belongs to the original domain Worlddata.ai.

Page Optimization Overview & Recommendations

Page size can be reduced by 335.0 kB (31%)

Content Size

1.1 MB

After Optimization

758.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Worlddata.ai main page is 1.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. 50% of websites need less resources to load. Images take 482.2 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 213.0 kB

  • Original 258.5 kB
  • After minification 199.6 kB
  • After compression 45.5 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 58.9 kB, which is 23% 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 213.0 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 15.6 kB

  • Original 482.2 kB
  • After minification 466.6 kB

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. World Data images are well optimized though.

JavaScript Optimization

-25%

Potential reduce by 62.0 kB

  • Original 246.8 kB
  • After minification 246.8 kB
  • After compression 184.7 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 62.0 kB or 25% of the original size.

CSS Optimization

-42%

Potential reduce by 44.3 kB

  • Original 105.7 kB
  • After minification 105.7 kB
  • After compression 61.4 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. Worlddata.ai needs all CSS files to be minified and compressed as it can save up to 44.3 kB or 42% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (74%)

Requests Now

50

After Optimization

13

  • Images
  • JavaScript
  • CSS

The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of World 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 14 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

worlddata.ai

worlddata.ai

230 ms

worlddata.ai

worlddata.ai

423 ms

5626831.js

5626831.js

73 ms

gtm.js

gtm.js

98 ms

bootstrap.min.css

bootstrap.min.css

160 ms

bootstrap-dropdownhover.min.css

bootstrap-dropdownhover.min.css

228 ms

owl.theme.default.min.css

owl.theme.default.min.css

232 ms

owl.carousel.min.css

owl.carousel.min.css

233 ms

owl.carousel.min.css

owl.carousel.min.css

240 ms

owl.theme.default.min.css

owl.theme.default.min.css

238 ms

styleProfile.css

styleProfile.css

236 ms

css2

css2

45 ms

jquery-ui.min.css

jquery-ui.min.css

301 ms

Main.css

Main.css

310 ms

main.css

main.css

375 ms

main-common.css

main-common.css

301 ms

landing-responsive.css

landing-responsive.css

383 ms

font-awesome.min.css

font-awesome.min.css

52 ms

brands.css

brands.css

312 ms

toastr.min.css

toastr.min.css

362 ms

LayoutLanding.css

LayoutLanding.css

367 ms

header.css

header.css

378 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

462 ms

widget.css

widget.css

425 ms

widget.js

widget.js

436 ms

Headerpartial.css

Headerpartial.css

438 ms

page_pricing.css

page_pricing.css

440 ms

rollup-marketing.css

rollup-marketing.css

445 ms

footer.css

footer.css

522 ms

footer_landing.css

footer_landing.css

522 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

590 ms

popper.min.js

popper.min.js

530 ms

bootstrap.min.js

bootstrap.min.js

531 ms

bootstrap-dropdownhover.js

bootstrap-dropdownhover.js

587 ms

toastr.js

toastr.js

587 ms

owl.carousel.min.js

owl.carousel.min.js

588 ms

Landing.js

Landing.js

588 ms

jquery.1.19.2.validate.min.js

jquery.1.19.2.validate.min.js

588 ms

jquery-ui.min.js

jquery-ui.min.js

680 ms

_layoutLanding.js

_layoutLanding.js

570 ms

js

js

35 ms

js

js

59 ms

css

css

14 ms

Logo.svg

Logo.svg

259 ms

LogoIH.svg

LogoIH.svg

261 ms

PCThumbnail.png

PCThumbnail.png

473 ms

Group%2030.png

Group%2030.png

294 ms

Landing%20-%201.png

Landing%20-%201.png

359 ms

Landing%20-%202.png

Landing%20-%202.png

381 ms

Landing%20-%203.png

Landing%20-%203.png

444 ms

Landing%20-%204.png

Landing%20-%204.png

414 ms

loader.gif

loader.gif

358 ms

check-green.png

check-green.png

422 ms

Group%2010.png

Group%2010.png

288 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

33 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

38 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

59 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

83 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

84 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

85 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

9 ms

fa-brands-400.woff

fa-brands-400.woff

222 ms

fa-brands-400.ttf

fa-brands-400.ttf

67 ms

fa-brands-400.svg

fa-brands-400.svg

67 ms

Accessibility Review

worlddata.ai accessibility score

87

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

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

High

Image elements do not have [alt] attributes

Best Practices

worlddata.ai best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

worlddata.ai SEO score

73

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

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 Worlddata.ai 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 Worlddata.ai 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

worlddata.ai

Open Graph description is not detected on the main page of World 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: