Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

geee.net

Guy Abbott v. MI5 Corruption

Page Load Speed

1.4 sec in total

First Response

338 ms

Resources Loaded

960 ms

Page Rendered

118 ms

geee.net screenshot

About Website

Welcome to geee.net homepage info - get ready to check Geee best content right away, or after learning these important things about geee.net

Blog about corruption and persecution by MI5 and the British Police Force

Visit geee.net

Key Findings

We analyzed Geee.net page load time and found that the first response time was 338 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 20% of websites can load faster.

Performance Metrics

geee.net performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.2 s

100/100

25%

SI (Speed Index)

Value1.5 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.1 s

100/100

10%

Network Requests Diagram

geee.net

338 ms

xx.css

105 ms

gee.js

191 ms

margspc.gif

105 ms

toptch2.jpg

97 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 10.9 kB (24%)

Content Size

45.4 kB

After Optimization

34.5 kB

In fact, the total size of Geee.net main page is 45.4 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. Images take 32.2 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 4.3 kB

  • Original 5.8 kB
  • After minification 4.5 kB
  • After compression 1.5 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.2 kB, which is 21% 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 4.3 kB or 74% of the original size.

Image Optimization

-1%

Potential reduce by 221 B

  • Original 32.2 kB
  • After minification 32.0 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. Geee images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 591 B

  • Original 1.0 kB
  • After minification 946 B
  • After compression 452 B

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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 591 B or 57% of the original size.

CSS Optimization

-91%

Potential reduce by 5.8 kB

  • Original 6.4 kB
  • After minification 5.1 kB
  • After compression 581 B

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. Geee.net needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 91% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

20

After Optimization

20

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

Accessibility Review

geee.net accessibility score

58

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

Image elements do not have [alt] attributes

Best Practices

geee.net best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

SEO Factors

geee.net SEO score

67

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geee.net 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 Geee.net main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Geee. 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: