Tools & Wizards About Us
foojay.io screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    41% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

foojay.io

Free Java & OpenJDK Info for Daily Java Usage | foojay

Page Load Speed

2.9 sec in total

First Response

42 ms

Resources Loaded

1.6 sec

Page Rendered

1.3 sec

foojay.io screenshot

About Website

Visit foojay.io now to see the best up-to-date Foojay content and also check out these interesting facts you probably never knew about foojay.io

A place for friends of OpenJDK, foojay provides user-focused Java and OpenJDK technical info and dashboards with free data for everyday Java developers.

Visit foojay.io

Key Findings

We analyzed Foojay.io page load time and found that the first response time was 42 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

foojay.io performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value3,770 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.059

98/100

15%

TTI (Time to Interactive)

Value13.8 s

10/100

10%

Network Requests Diagram

foojay.io

42 ms

foojay.io

510 ms

OtAutoBlock.js

183 ms

otSDKStub.js

190 ms

style.min.css

55 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 73% of them (27 requests) were addressed to the original Foojay.io, 8% (3 requests) were made to Cdn.cookielaw.org and 5% (2 requests) were made to Secure.gravatar.com. The less responsive or slowest element that took the longest time to load (510 ms) belongs to the original domain Foojay.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 245.9 kB (23%)

Content Size

1.0 MB

After Optimization

803.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Foojay.io 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 694.9 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 178.3 kB

  • Original 202.9 kB
  • After minification 153.3 kB
  • After compression 24.7 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 49.6 kB, which is 24% 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 178.3 kB or 88% of the original size.

Image Optimization

-8%

Potential reduce by 56.5 kB

  • Original 694.9 kB
  • After minification 638.4 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. Foojay images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 38 B

  • Original 7.5 kB
  • After minification 7.5 kB
  • After compression 7.4 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

-8%

Potential reduce by 11.1 kB

  • Original 143.8 kB
  • After minification 143.8 kB
  • After compression 132.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. Foojay.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (42%)

Requests Now

33

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

foojay.io

foojay.io

42 ms

foojay.io

foojay.io

510 ms

OtAutoBlock.js

OtAutoBlock.js

183 ms

otSDKStub.js

otSDKStub.js

190 ms

style.min.css

style.min.css

55 ms

styles.css

styles.css

80 ms

dashicons.min.css

dashicons.min.css

73 ms

frontend.css

frontend.css

72 ms

main.css

main.css

79 ms

enlighterjs.min.css

enlighterjs.min.css

126 ms

email-decode.min.js

email-decode.min.js

50 ms

index.js

index.js

76 ms

index.js

index.js

75 ms

main.js

main.js

103 ms

widgets.js

widgets.js

160 ms

enlighterjs.min.js

enlighterjs.min.js

96 ms

b352dcd3-1a32-40bc-9a54-75fc076d2cdb.json

b352dcd3-1a32-40bc-9a54-75fc076d2cdb.json

250 ms

css2

css2

154 ms

location

location

407 ms

logo.svg

logo.svg

358 ms

e19b2ed2a944b156752a540ad61e090d

e19b2ed2a944b156752a540ad61e090d

352 ms

Frank-7-XS-80x80.jpg

Frank-7-XS-80x80.jpg

254 ms

1516637392232-80x80.jpeg

1516637392232-80x80.jpeg

253 ms

cropped-1543939032821-80x80.jpeg

cropped-1543939032821-80x80.jpeg

213 ms

img-action-box-sms.png

img-action-box-sms.png

252 ms

tQPSyCtl_400x400-96x96.jpg

tQPSyCtl_400x400-96x96.jpg

213 ms

chandraguntur-96x96.jpg

chandraguntur-96x96.jpg

251 ms

johan-vos-avatar-96x96.jpeg

johan-vos-avatar-96x96.jpeg

252 ms

Jadon-96x96.jpg

Jadon-96x96.jpg

250 ms

hrAvch7J_400x400-96x96.jpeg

hrAvch7J_400x400-96x96.jpeg

423 ms

18vsTqAr_400x400-96x96.jpg

18vsTqAr_400x400-96x96.jpg

422 ms

b4kec7eV_400x400-96x96.jpg

b4kec7eV_400x400-96x96.jpg

256 ms

uXcsXQ5E_400x400-96x96.jpg

uXcsXQ5E_400x400-96x96.jpg

256 ms

home-about.png

home-about.png

430 ms

ae05e0405f84c2d03f2e2f68805c5681

ae05e0405f84c2d03f2e2f68805c5681

253 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

63 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

63 ms

Accessibility Review

foojay.io accessibility score

79

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-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

foojay.io 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

foojay.io SEO score

93

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foojay.io 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 Foojay.io 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

foojay.io

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