Tools & Wizards About Us
odata.org screenshot

Report Summary

  • 64

    Performance

    Renders faster than
    77% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

odata.org

OData - the Best Way to REST

Page Load Speed

1.9 sec in total

First Response

341 ms

Resources Loaded

1.4 sec

Page Rendered

170 ms

odata.org screenshot

About Website

Click here to check amazing OData content for Austria. Otherwise, check out these important facts you probably never knew about odata.org

OData, short for Open Data Protocol, is an open protocol to allow the creation and consumption of queryable and interoperable RESTful APIs in a simple and standard way.

Visit odata.org

Key Findings

We analyzed Odata.org page load time and found that the first response time was 341 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

odata.org performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value4.8 s

66/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.068

96/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

www.odata.org

341 ms

jquery-3.0.0.min.js

36 ms

bootstrap.min.css

75 ms

site.css

314 ms

syntax.css

315 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 73% of them (19 requests) were addressed to the original Odata.org, 8% (2 requests) were made to Cdnjs.cloudflare.com and 4% (1 request) were made to Ajax.aspnetcdn.com. The less responsive or slowest element that took the longest time to load (729 ms) belongs to the original domain Odata.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 97.7 kB (20%)

Content Size

500.6 kB

After Optimization

402.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Odata.org main page is 500.6 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. 25% of websites need less resources to load. Images take 346.3 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 24.4 kB

  • Original 30.8 kB
  • After minification 20.9 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 9.9 kB, which is 32% 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 24.4 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 14.6 kB

  • Original 346.3 kB
  • After minification 331.7 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. OData images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 57.6 kB

  • Original 98.9 kB
  • After minification 98.9 kB
  • After compression 41.3 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 57.6 kB or 58% of the original size.

CSS Optimization

-4%

Potential reduce by 1.1 kB

  • Original 24.6 kB
  • After minification 24.6 kB
  • After compression 23.5 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. Odata.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 13 (52%)

Requests Now

25

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OData. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.odata.org

www.odata.org

341 ms

jquery-3.0.0.min.js

jquery-3.0.0.min.js

36 ms

bootstrap.min.css

bootstrap.min.css

75 ms

site.css

site.css

314 ms

syntax.css

syntax.css

315 ms

autocomplete.css

autocomplete.css

385 ms

swiper.min.css

swiper.min.css

67 ms

magnific-popup.min.css

magnific-popup.min.css

83 ms

jquery-2.1.0.min.js

jquery-2.1.0.min.js

50 ms

bootstrap.min.js

bootstrap.min.js

61 ms

tabs.js

tabs.js

459 ms

combobox-autocomplete.js

combobox-autocomplete.js

458 ms

site.js

site.js

458 ms

jquery.swiftype.search.js

jquery.swiftype.search.js

461 ms

jquery.swiftype.autocomplete.js

jquery.swiftype.autocomplete.js

460 ms

OData-logo-e1393393068350.png

OData-logo-e1393393068350.png

439 ms

homepage_1.jpg

homepage_1.jpg

728 ms

homepage_2.jpg

homepage_2.jpg

660 ms

vs_code_for_odata.gif

vs_code_for_odata.gif

729 ms

xodata_tool.jpg

xodata_tool.jpg

514 ms

howtouse-03.png

howtouse-03.png

487 ms

howtouse-01.png

howtouse-01.png

511 ms

howtouse-02.png

howtouse-02.png

559 ms

howtouse-04.png

howtouse-04.png

584 ms

css

css

37 ms

font

font

21 ms

Accessibility Review

odata.org accessibility score

98

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

odata.org best practices score

58

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

odata.org SEO score

100

Search Engine Optimization Advices

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 uses legible font sizes

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

odata.org

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