Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

docs.openx.com

Docs Home - OpenX Docs

Page Load Speed

242 ms in total

First Response

28 ms

Resources Loaded

66 ms

Page Rendered

148 ms

docs.openx.com screenshot

About Website

Visit docs.openx.com now to see the best up-to-date Docs OpenX content for United States and also check out these interesting facts you probably never knew about docs.openx.com

OpenX Docs

Visit docs.openx.com

Key Findings

We analyzed Docs.openx.com page load time and found that the first response time was 28 ms and then it took 214 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

docs.openx.com performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

96/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

49/100

25%

SI (Speed Index)

Value1.4 s

100/100

10%

TBT (Total Blocking Time)

Value3,030 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.082

94/100

15%

TTI (Time to Interactive)

Value8.9 s

35/100

10%

Network Requests Diagram

docs.openx.com

28 ms

helpcenter.css

20 ms

openx.png

10 ms

Our browser made a total of 3 requests to load all elements on the main page. We found that all of those requests were addressed to Docs.openx.com and no external sources were called. The less responsive or slowest element that took the longest time to load (28 ms) belongs to the original domain Docs.openx.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 110.4 kB (60%)

Content Size

184.5 kB

After Optimization

74.1 kB

In fact, the total size of Docs.openx.com main page is 184.5 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. CSS take 143.2 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 3.2 kB

  • Original 3.6 kB
  • After minification 822 B
  • After compression 390 B

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 2.7 kB, which is 77% 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 3.2 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 37.7 kB
  • After minification 37.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. Docs OpenX images are well optimized though.

CSS Optimization

-75%

Potential reduce by 107.3 kB

  • Original 143.2 kB
  • After minification 117.8 kB
  • After compression 36.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. Docs.openx.com needs all CSS files to be minified and compressed as it can save up to 107.3 kB or 75% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

2

After Optimization

2

The browser has sent 2 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Docs OpenX. According to our analytics all requests are already optimized.

Accessibility Review

docs.openx.com accessibility score

84

Accessibility Issues

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

docs.openx.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

docs.openx.com SEO score

92

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

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Docs.openx.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Docs.openx.com 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 Docs OpenX. 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: