Tools & Wizards About Us
openstack.org screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

openstack.org

Open Source Cloud Computing Infrastructure - OpenStack

Page Load Speed

2.2 sec in total

First Response

199 ms

Resources Loaded

1.7 sec

Page Rendered

331 ms

openstack.org screenshot

About Website

Click here to check amazing Open Stack content for China. Otherwise, check out these important facts you probably never knew about openstack.org

OpenStack is an open source cloud computing infrastructure software project and is one of the three most active open source projects in the world.

Visit openstack.org

Key Findings

We analyzed Openstack.org page load time and found that the first response time was 199 ms and then it took 2 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

openstack.org performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value480 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.063

97/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

openstack.org

199 ms

openstack.org

337 ms

www.openstack.org

316 ms

main.css

49 ms

uc.js

35 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 41% of them (35 requests) were addressed to the original Openstack.org, 18% (15 requests) were made to Object-storage-ca-ymq-1.vexxhost.net and 16% (14 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (807 ms) relates to the external source Search.openstack.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 431.3 kB (26%)

Content Size

1.7 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Openstack.org main page is 1.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 35.0 kB

  • Original 45.8 kB
  • After minification 40.9 kB
  • After compression 10.8 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 4.9 kB, which is 11% 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 35.0 kB or 76% of the original size.

Image Optimization

-10%

Potential reduce by 46.3 kB

  • Original 466.0 kB
  • After minification 419.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. Open Stack images are well optimized though.

JavaScript Optimization

-33%

Potential reduce by 346.5 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 711.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 346.5 kB or 33% of the original size.

CSS Optimization

-4%

Potential reduce by 3.6 kB

  • Original 87.2 kB
  • After minification 87.2 kB
  • After compression 83.7 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. Openstack.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 40 (63%)

Requests Now

64

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

openstack.org

openstack.org

199 ms

openstack.org

openstack.org

337 ms

www.openstack.org

www.openstack.org

316 ms

main.css

main.css

49 ms

uc.js

uc.js

35 ms

css

css

50 ms

font-awesome.min.css

font-awesome.min.css

50 ms

all.min.css

all.min.css

42 ms

bootstrap.min.css

bootstrap.min.css

43 ms

home-page.css

home-page.css

59 ms

navigation_menu.css

navigation_menu.css

50 ms

dropdown.css

dropdown.css

101 ms

announcement-banner.css

announcement-banner.css

68 ms

home.css

home.css

99 ms

jquery.min.js

jquery.min.js

102 ms

jquery-migrate.min.js

jquery-migrate.min.js

98 ms

jquery-migrate.min.js

jquery-migrate.min.js

102 ms

jquery.entwine-dist.js

jquery.entwine-dist.js

108 ms

bootstrap.min.js

bootstrap.min.js

108 ms

js.cookie.js

js.cookie.js

189 ms

querystring.jquery.js

querystring.jquery.js

188 ms

shadowbox.js

shadowbox.js

162 ms

jquery.ticker.js

jquery.ticker.js

187 ms

jquery.tools.min.js

jquery.tools.min.js

187 ms

jcarousellite.min.js

jcarousellite.min.js

161 ms

navigation.js

navigation.js

219 ms

filetracking.jquery.js

filetracking.jquery.js

220 ms

updateProfileModal.js

updateProfileModal.js

221 ms

home.js

home.js

222 ms

clamp.min.js

clamp.min.js

219 ms

new-home-page.js

new-home-page.js

217 ms

api.js

api.js

40 ms

embed.min.js

embed.min.js

807 ms

main.js

main.js

326 ms

css2

css2

24 ms

gtm.js

gtm.js

123 ms

analytics.js

analytics.js

44 ms

bat.js

bat.js

81 ms

insight.min.js

insight.min.js

117 ms

css2

css2

71 ms

homepage-OpenStack-SFAs.svg

homepage-OpenStack-SFAs.svg

242 ms

OpenInfrastructureFoundation-icon-RGB.svg

OpenInfrastructureFoundation-icon-RGB.svg

309 ms

OpenInfra-Berlin2022.svg

OpenInfra-Berlin2022.svg

218 ms

js

js

70 ms

openstack-logo-full.svg

openstack-logo-full.svg

256 ms

homepage-overview-diagram-new.svg

homepage-overview-diagram-new.svg

279 ms

homepage-At-theEdge-Icon.svg

homepage-At-theEdge-Icon.svg

252 ms

homepage-On-Premises-Icon.svg

homepage-On-Premises-Icon.svg

253 ms

homepage-Public-Cloud-Icon.svg

homepage-Public-Cloud-Icon.svg

256 ms

Caracal-Logo-Vertical-2.png

Caracal-Logo-Vertical-2.png

311 ms

mirantis-lg.jpg

mirantis-lg.jpg

310 ms

CT-sm.png

CT-sm.png

321 ms

blizzard.jpg

blizzard.jpg

323 ms

walmart-sm.jpg

walmart-sm.jpg

386 ms

chinatelecom.jpg

chinatelecom.jpg

387 ms

OpenInfraFoundation-logo-RGB-horiz2.svg

OpenInfraFoundation-logo-RGB-horiz2.svg

387 ms

qrcode-for-gh-5cc38c749efd-1280.jpg

qrcode-for-gh-5cc38c749efd-1280.jpg

418 ms

fa-solid-900.woff

fa-solid-900.woff

285 ms

fa-regular-400.woff

fa-regular-400.woff

285 ms

fa-light-300.woff

fa-light-300.woff

309 ms

insight_tag_errors.gif

insight_tag_errors.gif

259 ms

quant.js

quant.js

190 ms

uwt.js

uwt.js

190 ms

js

js

99 ms

recaptcha__en.js

recaptcha__en.js

214 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf

212 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVcUwaEQXjM.ttf

265 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf

264 ms

collect

collect

98 ms

z7NOdRfiaC4Vd8hhoPzfb5vBTP266quhTfmrHsLu.ttf

z7NOdRfiaC4Vd8hhoPzfb5vBTP266quhTfmrHsLu.ttf

221 ms

z7NOdRfiaC4Vd8hhoPzfb5vBTP2D6quhTfmrHsLu.ttf

z7NOdRfiaC4Vd8hhoPzfb5vBTP2D6quhTfmrHsLu.ttf

220 ms

z7NOdRfiaC4Vd8hhoPzfb5vBTP1v7auhTfmrHsLu.ttf

z7NOdRfiaC4Vd8hhoPzfb5vBTP1v7auhTfmrHsLu.ttf

222 ms

z7NOdRfiaC4Vd8hhoPzfb5vBTP1d7auhTfmrHsLu.ttf

z7NOdRfiaC4Vd8hhoPzfb5vBTP1d7auhTfmrHsLu.ttf

221 ms

z7NOdRfiaC4Vd8hhoPzfb5vBTP0D7auhTfmrHsLu.ttf

z7NOdRfiaC4Vd8hhoPzfb5vBTP0D7auhTfmrHsLu.ttf

221 ms

KFOmCnqEu92Fr1Me5WZNCzc.ttf

KFOmCnqEu92Fr1Me5WZNCzc.ttf

218 ms

KFOlCnqEu92Fr1MmEU9vAx0_IsE.ttf

KFOlCnqEu92Fr1MmEU9vAx0_IsE.ttf

234 ms

KFOlCnqEu92Fr1MmSU5vAx0_IsE.ttf

KFOlCnqEu92Fr1MmSU5vAx0_IsE.ttf

239 ms

KFOkCnqEu92Fr1MmgWxPKTU1Kg.ttf

KFOkCnqEu92Fr1MmgWxPKTU1Kg.ttf

239 ms

KFOlCnqEu92Fr1MmWUlvAx0_IsE.ttf

KFOlCnqEu92Fr1MmWUlvAx0_IsE.ttf

232 ms

KFOlCnqEu92Fr1MmYUtvAx0_IsE.ttf

KFOlCnqEu92Fr1MmYUtvAx0_IsE.ttf

239 ms

fa-brands-400.woff

fa-brands-400.woff

154 ms

collect

collect

148 ms

adsct

adsct

225 ms

adsct

adsct

166 ms

ga-audiences

ga-audiences

68 ms

Accessibility Review

openstack.org accessibility score

77

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

openstack.org SEO score

73

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

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

openstack.org

Open Graph data is detected on the main page of Open Stack. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: