Tools & Wizards About Us
oraclize.it screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

oraclize.it

Provable - blockchain oracle service, enabling data-rich smart contracts

Page Load Speed

5 sec in total

First Response

329 ms

Resources Loaded

4.1 sec

Page Rendered

513 ms

oraclize.it screenshot

About Website

Click here to check amazing Oraclize content for India. Otherwise, check out these important facts you probably never knew about oraclize.it

Provable - the state of the art oracle service. Designing the safest data-transport-layer for blockchain that you can possibly get.

Visit oraclize.it

Key Findings

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

Performance Metrics

oraclize.it performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value8.0 s

21/100

10%

TBT (Total Blocking Time)

Value2,440 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.502

16/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

oraclize.it

329 ms

provable.xyz

390 ms

jquery.min.js

432 ms

bootstrap.css

389 ms

script.js

542 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 Oraclize.it, 89% (42 requests) were made to Provable.xyz and 6% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Provable.xyz.

Page Optimization Overview & Recommendations

Page size can be reduced by 76.1 kB (15%)

Content Size

491.7 kB

After Optimization

415.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oraclize.it main page is 491.7 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. 60% of websites need less resources to load. Images take 280.7 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 24.9 kB

  • Original 31.2 kB
  • After minification 24.0 kB
  • After compression 6.3 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 7.1 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 24.9 kB or 80% of the original size.

Image Optimization

-13%

Potential reduce by 35.9 kB

  • Original 280.7 kB
  • After minification 244.8 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. Obviously, Oraclize needs image optimization as it can save up to 35.9 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-6%

Potential reduce by 5.0 kB

  • Original 86.8 kB
  • After minification 86.8 kB
  • After compression 81.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.

CSS Optimization

-11%

Potential reduce by 10.3 kB

  • Original 93.0 kB
  • After minification 93.0 kB
  • After compression 82.8 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. Oraclize.it needs all CSS files to be minified and compressed as it can save up to 10.3 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (68%)

Requests Now

40

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oraclize.it

oraclize.it

329 ms

provable.xyz

provable.xyz

390 ms

jquery.min.js

jquery.min.js

432 ms

bootstrap.css

bootstrap.css

389 ms

script.js

script.js

542 ms

style.css

style.css

499 ms

content-box.css

content-box.css

529 ms

image-box.css

image-box.css

500 ms

animations.css

animations.css

805 ms

components.css

components.css

767 ms

flexslider.css

flexslider.css

853 ms

magnific-popup.css

magnific-popup.css

778 ms

contact-form.css

contact-form.css

946 ms

social.stream.css

social.stream.css

953 ms

skin.css

skin.css

1193 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

1116 ms

line-icons.min.css

line-icons.min.css

1147 ms

font-awesome.min.css

font-awesome.min.css

1794 ms

email-decode.min.js

email-decode.min.js

946 ms

bootstrap.min.js

bootstrap.min.js

1891 ms

imagesloaded.min.js

imagesloaded.min.js

1885 ms

parallax.min.js

parallax.min.js

1887 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

1893 ms

isotope.min.js

isotope.min.js

1897 ms

contact-form.js

contact-form.js

1911 ms

jquery.progress-counter.js

jquery.progress-counter.js

1906 ms

jquery.tab-accordion.js

jquery.tab-accordion.js

2047 ms

bootstrap.popover.min.js

bootstrap.popover.min.js

2056 ms

social.stream.min.js

social.stream.min.js

2052 ms

smooth.scroll.min.js

smooth.scroll.min.js

1901 ms

css

css

55 ms

loader.gif

loader.gif

681 ms

logo-horizontal-dark.png

logo-horizontal-dark.png

783 ms

gitter.png

gitter.png

646 ms

hp1b.png

hp1b.png

713 ms

bg-4.jpg

bg-4.jpg

870 ms

eco-gartner.png

eco-gartner.png

864 ms

eco-isp.png

eco-isp.png

1547 ms

eco-ey.png

eco-ey.png

1546 ms

eco-ucl.png

eco-ucl.png

1548 ms

eco-eea.png

eco-eea.png

1563 ms

eco-coinsilium.jpeg

eco-coinsilium.jpeg

1548 ms

va9I4kzIxd1KFrBoQeU.woff

va9I4kzIxd1KFrBoQeU.woff

166 ms

va9F4kzIxd1KFrjDY_Z4sKs.woff

va9F4kzIxd1KFrjDY_Z4sKs.woff

166 ms

va9F4kzIxd1KFrjTZPZ4sKs.woff

va9F4kzIxd1KFrjTZPZ4sKs.woff

166 ms

icomoon.woff

icomoon.woff

1383 ms

social.woff

social.woff

1083 ms

Accessibility Review

oraclize.it accessibility score

89

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

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

Links do not have a discernible name

Best Practices

oraclize.it best practices score

75

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

SEO Factors

oraclize.it SEO score

81

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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 Oraclize.it 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 Oraclize.it 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

oraclize.it

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