Tools & Wizards About Us
osgi.org screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    73% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 90% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

osgi.org

OSGi Working Group | The Eclipse Foundation

Page Load Speed

2.3 sec in total

First Response

150 ms

Resources Loaded

1.9 sec

Page Rendered

270 ms

osgi.org screenshot

About Website

Visit osgi.org now to see the best up-to-date OSGi content for Austria and also check out these interesting facts you probably never knew about osgi.org

The OSGi Working Group is a worldwide consortium of technology innovators that advances a proven and mature process to create open specifications that enable …

Visit osgi.org

Key Findings

We analyzed Osgi.org page load time and found that the first response time was 150 ms and then it took 2.2 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. This domain responded with an error, which can significantly jeopardize Osgi.org rating and web reputation

Performance Metrics

osgi.org performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value4.8 s

68/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.156

74/100

15%

TTI (Time to Interactive)

Value6.4 s

60/100

10%

Network Requests Diagram

osgi.org

150 ms

www.osgi.org

232 ms

www.osgi.org

385 ms

jquery.min.js

75 ms

jquery.matchHeight.js

73 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 85% of them (67 requests) were addressed to the original Osgi.org, 6% (5 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (717 ms) belongs to the original domain Osgi.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 406.9 kB (41%)

Content Size

997.7 kB

After Optimization

590.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 54.3 kB

  • Original 66.3 kB
  • After minification 60.3 kB
  • After compression 12.1 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 54.3 kB or 82% of the original size.

Image Optimization

-10%

Potential reduce by 53.3 kB

  • Original 511.6 kB
  • After minification 458.3 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. OSGi images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 212.7 kB

  • Original 308.8 kB
  • After minification 268.5 kB
  • After compression 96.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 212.7 kB or 69% of the original size.

CSS Optimization

-78%

Potential reduce by 86.6 kB

  • Original 110.9 kB
  • After minification 90.7 kB
  • After compression 24.3 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. Osgi.org needs all CSS files to be minified and compressed as it can save up to 86.6 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (46%)

Requests Now

68

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

osgi.org

osgi.org

150 ms

www.osgi.org

www.osgi.org

232 ms

www.osgi.org

www.osgi.org

385 ms

jquery.min.js

jquery.min.js

75 ms

jquery.matchHeight.js

jquery.matchHeight.js

73 ms

cnss.css

cnss.css

142 ms

newsscrollcss.css

newsscrollcss.css

207 ms

css

css

73 ms

style.css

style.css

209 ms

css

css

117 ms

style.css

style.css

211 ms

font-awesome.css

font-awesome.css

211 ms

admin_style.min.css

admin_style.min.css

212 ms

jquery.js

jquery.js

279 ms

jquery-migrate.min.js

jquery-migrate.min.js

273 ms

cnss.js

cnss.js

276 ms

jv.js

jv.js

274 ms

jquery.newsTicker.js

jquery.newsTicker.js

273 ms

stylesheet.min.css

stylesheet.min.css

354 ms

font-awesome.min.css

font-awesome.min.css

46 ms

default.css

default.css

354 ms

flexslider.css

flexslider.css

355 ms

public.css

public.css

355 ms

public.css

public.css

355 ms

core.min.js

core.min.js

356 ms

widget.min.js

widget.min.js

357 ms

mouse.min.js

mouse.min.js

429 ms

sortable.min.js

sortable.min.js

428 ms

qppr_frontend_script.min.js

qppr_frontend_script.min.js

428 ms

theme.js

theme.js

433 ms

wp-embed.min.js

wp-embed.min.js

428 ms

_scripts.min.js

_scripts.min.js

432 ms

starter.min.js

starter.min.js

527 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

526 ms

floatmenu.js

floatmenu.js

440 ms

ga.js

ga.js

87 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

419 ms

__utm.gif

__utm.gif

38 ms

solid.png

solid.png

587 ms

search.jpg

search.jpg

223 ms

logo.jpg

logo.jpg

575 ms

twitter.jpg

twitter.jpg

576 ms

other.jpg

other.jpg

577 ms

linkedin.jpg

linkedin.jpg

577 ms

GitHub-Mark-32px.png

GitHub-Mark-32px.png

577 ms

loading.gif

loading.gif

578 ms

blueblockbottom.png

blueblockbottom.png

580 ms

icon_developer.png

icon_developer.png

579 ms

icon_business.png

icon_business.png

580 ms

icon_enroute.png

icon_enroute.png

581 ms

Paremus-Member-Slider.jpeg

Paremus-Member-Slider.jpeg

582 ms

IBM1.jpg

IBM1.jpg

583 ms

Oracle-member-slider.jpeg

Oracle-member-slider.jpeg

585 ms

Luminis_Basis_ComplVector_ZondMasker.jpg

Luminis_Basis_ComplVector_ZondMasker.jpg

583 ms

SAG-Logo_150x75.jpg

SAG-Logo_150x75.jpg

586 ms

2014-Liferay-Logo-Horizontal-1.png

2014-Liferay-Logo-Horizontal-1.png

587 ms

20150713_ProSystBG-RGB_72dpi_150x75.png

20150713_ProSystBG-RGB_72dpi_150x75.png

547 ms

NTT.jpg

NTT.jpg

545 ms

Cloudyle.jpg

Cloudyle.jpg

546 ms

makewave-150x75.png

makewave-150x75.png

547 ms

HW_POS_RGB_Horizontal1.jpg

HW_POS_RGB_Horizontal1.jpg

717 ms

Adobe2.jpeg

Adobe2.jpeg

575 ms

Brandmark_Ha_E_Color-copy-150x75.jpeg

Brandmark_Ha_E_Color-copy-150x75.jpeg

574 ms

_dCzxpXzIS3sL-gdJWAP8A.ttf

_dCzxpXzIS3sL-gdJWAP8A.ttf

115 ms

M7no6oPkwKYJkedjB1wqEvesZW2xOQ-xsNqO47m55DA.ttf

M7no6oPkwKYJkedjB1wqEvesZW2xOQ-xsNqO47m55DA.ttf

156 ms

VGEV9-DrblisWOWLbK-1XPesZW2xOQ-xsNqO47m55DA.ttf

VGEV9-DrblisWOWLbK-1XPesZW2xOQ-xsNqO47m55DA.ttf

524 ms

nj47mAZe0mYUIySgfn0wpQ.ttf

nj47mAZe0mYUIySgfn0wpQ.ttf

523 ms

DvlFBScY1r-FMtZSYIYoYw.ttf

DvlFBScY1r-FMtZSYIYoYw.ttf

521 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

666 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

23 ms

DT2.jpeg

DT2.jpeg

504 ms

spotlight.jpg

spotlight.jpg

504 ms

tools.jpg

tools.jpg

519 ms

internet.jpg

internet.jpg

521 ms

enterprises.jpg

enterprises.jpg

549 ms

cloud.jpg

cloud.jpg

557 ms

blog.jpg

blog.jpg

493 ms

wiki.png

wiki.png

495 ms

bigpuzzle.jpg

bigpuzzle.jpg

251 ms

Accessibility Review

osgi.org accessibility score

96

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

Best Practices

osgi.org 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

osgi.org SEO score

89

Search Engine Optimization Advices

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

osgi.org

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