Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

pgptool.github.io

PGPTool - use this tool to encrypt and decrypt PGP files. OpenPGP compatible

Page Load Speed

2 sec in total

First Response

15 ms

Resources Loaded

918 ms

Page Rendered

1 sec

pgptool.github.io screenshot

About Website

Welcome to pgptool.github.io homepage info - get ready to check PGPTool Github best content for China right away, or after learning these important things about pgptool.github.io

PGP for Windows, MacOS and linux. Desktop application to encrypt and decrypt PGP files. It's free and easy to use. OpenPGP compatible.

Visit pgptool.github.io

Key Findings

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

Performance Metrics

pgptool.github.io performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

21/100

25%

SI (Speed Index)

Value4.4 s

75/100

10%

TBT (Total Blocking Time)

Value1,160 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

pgptool.github.io

15 ms

pgptool.github.io

33 ms

bootstrap.min.css

27 ms

style.css

33 ms

font-awesome.min.css

36 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 42% of them (19 requests) were addressed to the original Pgptool.github.io, 20% (9 requests) were made to Fonts.gstatic.com and 11% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (360 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 168.9 kB (15%)

Content Size

1.1 MB

After Optimization

948.1 kB

In fact, the total size of Pgptool.github.io main page is 1.1 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. 55% of websites need less resources to load. Images take 850.0 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 21.7 kB

  • Original 28.4 kB
  • After minification 22.2 kB
  • After compression 6.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 6.1 kB, which is 22% 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 21.7 kB or 76% of the original size.

Image Optimization

-17%

Potential reduce by 144.6 kB

  • Original 850.0 kB
  • After minification 705.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. Obviously, PGPTool Github needs image optimization as it can save up to 144.6 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 2.6 kB

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

-0%

Potential reduce by 0 B

  • Original 58.7 kB
  • After minification 58.7 kB
  • After compression 58.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. Pgptool.github.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 16 (48%)

Requests Now

33

After Optimization

17

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

Accessibility Review

pgptool.github.io 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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

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

pgptool.github.io best practices score

75

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

pgptool.github.io SEO score

85

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

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 Pgptool.github.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 Pgptool.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 description is not detected on the main page of PGPTool Github. 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: