Tools & Wizards About Us
vho.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

vho.org

Historical Revisionism by Vrij Historisch Onderzoek

Page Load Speed

2.3 sec in total

First Response

151 ms

Resources Loaded

2 sec

Page Rendered

190 ms

vho.org screenshot

About Website

Visit vho.org now to see the best up-to-date Vho content for Germany and also check out these interesting facts you probably never knew about vho.org

Revisionist publications online (mainly in German), and for purchase (deutsch, fran?ais, netherlands, English, italiano). Index of revisionist publications available online, index of censorship.

Visit vho.org

Key Findings

We analyzed Vho.org page load time and found that the first response time was 151 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

vho.org performance score

0

Network Requests Diagram

vho.org

151 ms

style.css

88 ms

advertiser.js

90 ms

advertiser-e.js

150 ms

978-1-59148-027-3-Coverl.jpg

1255 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 64% of them (14 requests) were addressed to the original Vho.org, 32% (7 requests) were made to Shop.codoh.com and 5% (1 request) were made to Imgssl.constantcontact.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Vho.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 8.0 kB (62%)

Content Size

12.8 kB

After Optimization

4.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vho.org main page is 12.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. 25% of websites need less resources to load. HTML takes 8.0 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 5.4 kB

  • Original 8.0 kB
  • After minification 7.2 kB
  • After compression 2.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. 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 5.4 kB or 68% of the original size.

Image Optimization

-23%

Potential reduce by 440 B

  • Original 1.9 kB
  • After minification 1.5 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, Vho needs image optimization as it can save up to 440 B or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-75%

Potential reduce by 2.0 kB

  • Original 2.6 kB
  • After minification 2.3 kB
  • After compression 641 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 2.0 kB or 75% of the original size.

CSS Optimization

-50%

Potential reduce by 155 B

  • Original 309 B
  • After minification 257 B
  • After compression 154 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. Vho.org needs all CSS files to be minified and compressed as it can save up to 155 B or 50% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

15

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vho.org

vho.org

151 ms

style.css

style.css

88 ms

advertiser.js

advertiser.js

90 ms

advertiser-e.js

advertiser-e.js

150 ms

978-1-59148-027-3-Coverl.jpg

978-1-59148-027-3-Coverl.jpg

1255 ms

9781591480341-Vorlesungen-Coverl.jpg

9781591480341-Vorlesungen-Coverl.jpg

1385 ms

978-1-59148-030-3-Coverl.jpg

978-1-59148-030-3-Coverl.jpg

1381 ms

342l.jpg

342l.jpg

1380 ms

343l.jpg

343l.jpg

1381 ms

safe_subscribe_logo.gif

safe_subscribe_logo.gif

35 ms

back.jpg

back.jpg

51 ms

HHS.gif

HHS.gif

117 ms

titleflags.gif

titleflags.gif

91 ms

HHS-D.gif

HHS-D.gif

143 ms

GBdownload.png

GBdownload.png

109 ms

shop.codoh.com

shop.codoh.com

292 ms

shop.codoh.com

shop.codoh.com

285 ms

shop.codoh.com

shop.codoh.com

206 ms

shop.codoh.com

shop.codoh.com

261 ms

shop.codoh.com

shop.codoh.com

269 ms

shop.codoh.com

shop.codoh.com

264 ms

shop.codoh.com

shop.codoh.com

354 ms

SEO Factors

vho.org SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vho.org 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 Vho.org main page’s claimed encoding is windows-1252. 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

vho.org

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