Tools & Wizards About Us
eclipse.org screenshot

Report Summary

  • 64

    Performance

    Renders faster than
    77% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

eclipse.org

The Community for Open Collaboration and Innovation | The Eclipse Foundation

Page Load Speed

789 ms in total

First Response

46 ms

Resources Loaded

481 ms

Page Rendered

262 ms

eclipse.org screenshot

About Website

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

The Eclipse Foundation provides our global community of individuals and organisations with a mature, scalable, and business-friendly environment for open source …

Visit eclipse.org

Key Findings

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

eclipse.org performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

76/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.063

97/100

15%

TTI (Time to Interactive)

Value6.3 s

61/100

10%

Network Requests Diagram

eclipse.org

46 ms

www.eclipse.org

111 ms

styles.css

69 ms

homepage.css

65 ms

css2

35 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 80% of them (12 requests) were addressed to the original Eclipse.org, 7% (1 request) were made to Fonts.googleapis.com and 7% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (146 ms) belongs to the original domain Eclipse.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 34.5 kB (7%)

Content Size

482.1 kB

After Optimization

447.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eclipse.org main page is 482.1 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. 45% of websites need less resources to load. Images take 203.6 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 28.4 kB

  • Original 34.4 kB
  • After minification 34.4 kB
  • After compression 6.0 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 28.4 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 3.3 kB

  • Original 203.6 kB
  • After minification 200.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. Eclipse images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.0 kB

  • Original 191.1 kB
  • After minification 191.1 kB
  • After compression 189.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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 919 B

  • Original 53.1 kB
  • After minification 53.1 kB
  • After compression 52.2 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. Eclipse.org has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

12

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eclipse.org

eclipse.org

46 ms

www.eclipse.org

www.eclipse.org

111 ms

styles.css

styles.css

69 ms

homepage.css

homepage.css

65 ms

css2

css2

35 ms

main.js

main.js

146 ms

gtm.js

gtm.js

74 ms

eclipse-foundation-grey-orange.svg

eclipse-foundation-grey-orange.svg

35 ms

eclipse-home-bg.jpg

eclipse-home-bg.jpg

122 ms

announcements.jpg

announcements.jpg

96 ms

community-news.jpg

community-news.jpg

96 ms

homepage-mid-banner.png

homepage-mid-banner.png

123 ms

back-to-top.png

back-to-top.png

102 ms

font

font

34 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

46 ms

Accessibility Review

eclipse.org accessibility score

91

Accessibility Issues

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-*] attributes are not valid or misspelled

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.

Best Practices

eclipse.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

eclipse.org SEO score

83

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

eclipse.org

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