Report Summary

  • 91

    Performance

    Renders faster than
    91% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

jbzteam.github.io

JBZ CTF Team | We Criuz, che si owna di bello?

Page Load Speed

694 ms in total

First Response

88 ms

Resources Loaded

408 ms

Page Rendered

198 ms

jbzteam.github.io screenshot

About Website

Click here to check amazing JBZ Team Github content for China. Otherwise, check out these important facts you probably never knew about jbzteam.github.io

We Criuz, che si owna di bello?

Visit jbzteam.github.io

Key Findings

We analyzed Jbzteam.github.io page load time and found that the first response time was 88 ms and then it took 606 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

jbzteam.github.io performance score

91

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value3.2 s

94/100

10%

Network Requests Diagram

jbzteam.github.io

88 ms

jbz.team

138 ms

css

47 ms

main.css

18 ms

u-4n0qyriQwlOrhSvowK_l521wRZWMf_.ttf

55 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that 13% of them (1 request) were addressed to the original Jbzteam.github.io, 50% (4 requests) were made to Fonts.gstatic.com and 25% (2 requests) were made to Jbz.team. The less responsive or slowest element that took the longest time to load (138 ms) relates to the external source Jbz.team.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.9 kB (67%)

Content Size

11.8 kB

After Optimization

3.9 kB

In fact, the total size of Jbzteam.github.io main page is 11.8 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. Only 5% of websites need less resources to load. HTML takes 11.8 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 7.9 kB

  • Original 11.8 kB
  • After minification 9.7 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 2.2 kB, which is 18% 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 7.9 kB or 67% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

2

After Optimization

2

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

Accessibility Review

jbzteam.github.io accessibility score

79

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Links do not have a discernible name

Best Practices

jbzteam.github.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

SEO Factors

jbzteam.github.io SEO score

97

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jbzteam.github.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Jbzteam.github.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

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: