Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

onvif.org

Home - ONVIF

Page Load Speed

964 ms in total

First Response

30 ms

Resources Loaded

735 ms

Page Rendered

199 ms

onvif.org screenshot

About Website

Welcome to onvif.org homepage info - get ready to check ONVIF best content for United States right away, or after learning these important things about onvif.org

Home

Visit onvif.org

Key Findings

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

Performance Metrics

onvif.org performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value620 ms

48/100

30%

CLS (Cumulative Layout Shift)

Value0.148

76/100

15%

TTI (Time to Interactive)

Value7.7 s

46/100

10%

Network Requests Diagram

onvif.org

30 ms

www.onvif.org

61 ms

default.css

10 ms

module.css

14 ms

skin.css

12 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 87% of them (47 requests) were addressed to the original Onvif.org, 6% (3 requests) were made to Google.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (573 ms) belongs to the original domain Onvif.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 552.0 kB (46%)

Content Size

1.2 MB

After Optimization

657.4 kB

In fact, the total size of Onvif.org main page is 1.2 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 533.1 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 37.3 kB

  • Original 46.7 kB
  • After minification 41.8 kB
  • After compression 9.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 37.3 kB or 80% of the original size.

Image Optimization

-9%

Potential reduce by 47.1 kB

  • Original 533.1 kB
  • After minification 486.0 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. ONVIF images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 365.2 kB

  • Original 510.3 kB
  • After minification 484.0 kB
  • After compression 145.1 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 365.2 kB or 72% of the original size.

CSS Optimization

-86%

Potential reduce by 102.4 kB

  • Original 119.4 kB
  • After minification 94.6 kB
  • After compression 17.0 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. Onvif.org needs all CSS files to be minified and compressed as it can save up to 102.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (60%)

Requests Now

50

After Optimization

20

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

Accessibility Review

onvif.org accessibility score

83

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.

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

onvif.org best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

onvif.org SEO score

76

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

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

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