Tools & Wizards About Us
histo.com screenshot

Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

histo.com

Monographies villes villages de France. Achat livres histoire. Librairie d'histoire locale

Page Load Speed

2.7 sec in total

First Response

403 ms

Resources Loaded

1.5 sec

Page Rendered

705 ms

histo.com screenshot

About Website

Visit histo.com now to see the best up-to-date Histo content for France and also check out these interesting facts you probably never knew about histo.com

Monographies des communes, départements, régions de France. Livres d'histoire des villes et villages de France. Collection d'ouvrages d'histoire locale. Réédition de livres anciens sur les communes de...

Visit histo.com

Key Findings

We analyzed Histo.com page load time and found that the first response time was 403 ms and then it took 2.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

histo.com performance score

0

Network Requests Diagram

histo.com

403 ms

vide.htm

84 ms

menu.htm

158 ms

haut.htm

162 ms

accueil.php

344 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 93% of them (55 requests) were addressed to the original Histo.com, 7% (4 requests) were made to Logv20.xiti.com. The less responsive or slowest element that took the longest time to load (552 ms) belongs to the original domain Histo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 10.5 kB (43%)

Content Size

24.7 kB

After Optimization

14.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Histo.com main page is 24.7 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 10% of websites need less resources to load. HTML takes 12.5 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 8.9 kB

  • Original 12.5 kB
  • After minification 12.5 kB
  • After compression 3.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 8.9 kB or 71% of the original size.

Image Optimization

-14%

Potential reduce by 1.5 kB

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

JavaScript Optimization

-4%

Potential reduce by 31 B

  • Original 719 B
  • After minification 719 B
  • After compression 688 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. This website has mostly compressed JavaScripts.

CSS Optimization

-13%

Potential reduce by 64 B

  • Original 481 B
  • After minification 481 B
  • After compression 417 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. Histo.com needs all CSS files to be minified and compressed as it can save up to 64 B or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (58%)

Requests Now

55

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

histo.com

histo.com

403 ms

vide.htm

vide.htm

84 ms

menu.htm

menu.htm

158 ms

haut.htm

haut.htm

162 ms

accueil.php

accueil.php

344 ms

menu2.htm

menu2.htm

136 ms

vide0.htm

vide0.htm

180 ms

vide2.htm

vide2.htm

179 ms

histo.css

histo.css

202 ms

fondmenu.gif

fondmenu.gif

125 ms

transp.gif

transp.gif

125 ms

logo1.gif

logo1.gif

125 ms

logo1b.gif

logo1b.gif

126 ms

logo1c.gif

logo1c.gif

127 ms

histo.gif

histo.gif

191 ms

monog.gif

monog.gif

185 ms

1.gif

1.gif

190 ms

2.gif

2.gif

190 ms

3.gif

3.gif

220 ms

4.gif

4.gif

208 ms

5.gif

5.gif

253 ms

6.gif

6.gif

281 ms

7.gif

7.gif

281 ms

8.gif

8.gif

281 ms

9.gif

9.gif

289 ms

10.gif

10.gif

316 ms

11.gif

11.gif

348 ms

12.gif

12.gif

366 ms

13.gif

13.gif

361 ms

14.gif

14.gif

365 ms

15.gif

15.gif

369 ms

hit.xiti

hit.xiti

39 ms

histo.js

histo.js

346 ms

fondhaut.gif

fondhaut.gif

356 ms

logo2.gif

logo2.gif

372 ms

contact1.gif

contact1.gif

382 ms

contact2.gif

contact2.gif

380 ms

info1.gif

info1.gif

375 ms

info2.gif

info2.gif

436 ms

slogan.gif

slogan.gif

437 ms

transp.gif

transp.gif

455 ms

collections.gif

collections.gif

456 ms

journal.gif

journal.gif

468 ms

proposer.gif

proposer.gif

471 ms

libraires.gif

libraires.gif

526 ms

hit.xiti

hit.xiti

61 ms

commande.gif

commande.gif

479 ms

fond.gif

fond.gif

497 ms

3269.jpg

3269.jpg

490 ms

3264.jpg

3264.jpg

510 ms

3262.jpg

3262.jpg

512 ms

3261.jpg

3261.jpg

552 ms

hit.xiti

hit.xiti

43 ms

31032014.js

31032014.js

284 ms

cat2013.gif

cat2013.gif

283 ms

puce.gif

puce.gif

295 ms

index.htm

index.htm

430 ms

vignette.jpg

vignette.jpg

85 ms

hit.xiti

hit.xiti

10 ms

Accessibility Review

histo.com accessibility score

33

Accessibility Issues

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

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

Best Practices

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

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

histo.com SEO score

67

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Histo.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Histo.com 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

histo.com

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