Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 73% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    65% of websites

  • 73

    SEO

    Google-friendlier than
    40% of websites

eclipse.org

Enabling Open Innovation & Collaboration | The Eclipse Foundation

Page Load Speed

1.3 sec in total

First Response

88 ms

Resources Loaded

944 ms

Page Rendered

272 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 - home to a global community, the Eclipse IDE, Jakarta EE and over 415 open source projects, including runtimes, tools and frameworks.

Visit eclipse.org

Key Findings

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

Performance Metrics

eclipse.org performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

58/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

70/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.506

16/100

15%

TTI (Time to Interactive)

Value6.9 s

54/100

10%

Network Requests Diagram

eclipse.org

88 ms

www.eclipse.org

234 ms

css

26 ms

styles.min.css

98 ms

show_ads.js

52 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 43% of them (23 requests) were addressed to the original Eclipse.org, 15% (8 requests) were made to Google.com and 7% (4 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (234 ms) belongs to the original domain Eclipse.org.

Page Optimization Overview & Recommendations

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

Content Size

1.0 MB

After Optimization

559.4 kB

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

HTML Optimization

-77%

Potential reduce by 29.7 kB

  • Original 38.6 kB
  • After minification 34.7 kB
  • After compression 8.9 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 29.7 kB or 77% of the original size.

Image Optimization

-8%

Potential reduce by 32.4 kB

  • Original 414.4 kB
  • After minification 381.9 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

-63%

Potential reduce by 211.4 kB

  • Original 333.5 kB
  • After minification 332.5 kB
  • After compression 122.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 211.4 kB or 63% of the original size.

CSS Optimization

-82%

Potential reduce by 209.6 kB

  • Original 256.0 kB
  • After minification 251.4 kB
  • After compression 46.4 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 needs all CSS files to be minified and compressed as it can save up to 209.6 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (28%)

Requests Now

46

After Optimization

33

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

Accessibility Review

eclipse.org accessibility score

87

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

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

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

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

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