Tools & Wizards About Us
hg8.sh screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

hg8.sh

hg8's Notes — My notes about infosec world. Pentest/Bug Bounty/CTF Writeups.

Page Load Speed

508 ms in total

First Response

97 ms

Resources Loaded

348 ms

Page Rendered

63 ms

hg8.sh screenshot

About Website

Click here to check amazing Hg 8 content. Otherwise, check out these important facts you probably never knew about hg8.sh

Hi there, my name is Hugo, I am Information Security Researcher and Capture The Flag enthusiast. I set up this website to keep notes of my infosec journey including some various work and especially CT

Visit hg8.sh

Key Findings

We analyzed Hg8.sh page load time and found that the first response time was 97 ms and then it took 411 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

hg8.sh performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

96/100

10%

LCP (Largest Contentful Paint)

Value1.4 s

100/100

25%

SI (Speed Index)

Value1.4 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value1.4 s

100/100

10%

Network Requests Diagram

hg8.sh

97 ms

style.css

30 ms

all.min.css

80 ms

email-decode.min.js

26 ms

jquery.min.js

64 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that all of those requests were addressed to Hg8.sh and no external sources were called. The less responsive or slowest element that took the longest time to load (97 ms) belongs to the original domain Hg8.sh.

Page Optimization Overview & Recommendations

Page size can be reduced by 5.1 kB (45%)

Content Size

11.2 kB

After Optimization

6.1 kB

  • HTML
  • JavaScript

In fact, the total size of Hg8.sh main page is 11.2 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. 20% of websites need less resources to load. HTML takes 6.7 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 5.1 kB

  • Original 6.7 kB
  • After minification 5.2 kB
  • After compression 1.6 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 1.5 kB, which is 23% 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 5.1 kB or 76% of the original size.

JavaScript Optimization

-0%

Potential reduce by 17 B

  • Original 4.5 kB
  • After minification 4.5 kB
  • After compression 4.5 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.

Requests Breakdown

Number of requests can be reduced by 5 (56%)

Requests Now

9

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hg8.sh

hg8.sh

97 ms

style.css

style.css

30 ms

all.min.css

all.min.css

80 ms

email-decode.min.js

email-decode.min.js

26 ms

jquery.min.js

jquery.min.js

64 ms

main.js

main.js

65 ms

rocket-loader.min.js

rocket-loader.min.js

12 ms

logo.webp

logo.webp

42 ms

jquery.min.js

jquery.min.js

35 ms

fa-brands-400.woff

fa-brands-400.woff

50 ms

fa-solid-900.woff

fa-solid-900.woff

41 ms

fa-regular-400.woff

fa-regular-400.woff

49 ms

main.js

main.js

24 ms

Accessibility Review

hg8.sh accessibility score

86

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.

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

hg8.sh best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

hg8.sh SEO score

98

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

    EN

  • Encoding

    UTF-8

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

hg8.sh

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: