Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 79% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

siegate.com

GitHub - GridProtectionAlliance/SIEGate: Secure Information Exchange Gateway

Page Load Speed

1.2 sec in total

First Response

79 ms

Resources Loaded

863 ms

Page Rendered

242 ms

About Website

Click here to check amazing SIEGate content. Otherwise, check out these important facts you probably never knew about siegate.com

Secure Information Exchange Gateway. Contribute to GridProtectionAlliance/SIEGate development by creating an account on GitHub.

Visit siegate.com

Key Findings

We analyzed Siegate.com page load time and found that the first response time was 79 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

siegate.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

37/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value2,570 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value10.5 s

24/100

10%

Network Requests Diagram

siegate.com

79 ms

SIEGate

517 ms

light-0eace2597ca3.css

94 ms

dark-a167e256da9c.css

96 ms

primer-primitives-2ef2a46b27ee.css

78 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Siegate.com, 92% (73 requests) were made to Github.githubassets.com and 4% (3 requests) were made to Camo.githubusercontent.com. The less responsive or slowest element that took the longest time to load (517 ms) relates to the external source Github.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 300.3 kB (25%)

Content Size

1.2 MB

After Optimization

924.5 kB

In fact, the total size of Siegate.com main page is 1.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 704.7 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 258.6 kB

  • Original 309.7 kB
  • After minification 301.3 kB
  • After compression 51.1 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 258.6 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 54.8 kB
  • After minification 54.8 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. SIEGate images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 12.4 kB

  • Original 704.7 kB
  • After minification 704.7 kB
  • After compression 692.3 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

-19%

Potential reduce by 29.4 kB

  • Original 155.8 kB
  • After minification 150.4 kB
  • After compression 126.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. Siegate.com needs all CSS files to be minified and compressed as it can save up to 29.4 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 71 (93%)

Requests Now

76

After Optimization

5

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

Accessibility Review

siegate.com accessibility score

92

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 do not match their roles

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

siegate.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

siegate.com SEO score

84

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 Siegate.com 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 Siegate.com 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 SIEGate. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: