1.8 sec in total
253 ms
1 sec
525 ms
Welcome to firehist.org homepage info - get ready to check Firehist best content right away, or after learning these important things about firehist.org
Ingénieur Front-End Enthousiaste, Longearet Benjamin alias firehist. Tech Lead et Architecte Front-End chez Teads.
Visit firehist.orgWe analyzed Firehist.org page load time and found that the first response time was 253 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
firehist.org performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value5.1 s
25/100
25%
Value3.9 s
82/100
10%
Value430 ms
64/100
30%
Value0.642
9/100
15%
Value5.2 s
74/100
10%
253 ms
144 ms
29 ms
24 ms
56 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Firehist.org, 80% (35 requests) were made to Portfolio.firehist.org and 11% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (261 ms) relates to the external source Portfolio.firehist.org.
Page size can be reduced by 226.2 kB (70%)
323.5 kB
97.2 kB
In fact, the total size of Firehist.org main page is 323.5 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. 40% of websites need less resources to load. CSS take 190.8 kB which makes up the majority of the site volume.
Potential reduce by 29.9 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 5.4 kB, which is 16% 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 29.9 kB or 87% of the original size.
Potential reduce by 121 B
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. Firehist images are well optimized though.
Potential reduce by 32.0 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 32.0 kB or 60% of the original size.
Potential reduce by 164.3 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. Firehist.org needs all CSS files to be minified and compressed as it can save up to 164.3 kB or 86% of the original size.
Number of requests can be reduced by 8 (24%)
34
26
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Firehist. 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.
firehist.org
253 ms
portfolio.firehist.org
144 ms
vendor.48b336bb.css
29 ms
css
24 ms
main.a1fec109.css
56 ms
vendor.ec144427.js
102 ms
angulartics.js
41 ms
angulartics-ga.js
73 ms
scripts.16d2762c.js
74 ms
analytics.js
10 ms
collect
29 ms
blnavbar.html
169 ms
blgame.html
25 ms
blsectionheader.html
185 ms
blsectionabout.html
179 ms
blsectioncv.html
210 ms
blsectionmanifeste.html
94 ms
blsectiondeveloper.html
254 ms
blsectioncreation.html
221 ms
blsectionfooter.html
256 ms
roboto-regular-webfont.9cdd0ccc.woff
261 ms
rocket.9372d72d.svg
178 ms
eye.ec92312f.png
175 ms
sky_cloud_01.dad7c109.svg
164 ms
rocket.79139c8f.png
164 ms
hand.f9edd8b2.png
170 ms
arrow-down-blue.abf86531.png
171 ms
hat.3064e6c8.png
139 ms
sky_cloud_02.df4e6bf7.svg
117 ms
sky_background.a2d5725d.svg
119 ms
arrow-down-white.484a8754.png
121 ms
finger.b3585116.png
118 ms
bookshelf.png
81 ms
eye.png
77 ms
hand.png
76 ms
dev.c3e8ff3f.png
78 ms
pastille_twitter.cd968954.png
68 ms
pastille_github.0f986bd8.png
68 ms
pastille_linkedin.60c20200.png
72 ms
0DeoTBMnW4sOpD0Zb8OQSALUuEpTyoUstqEm5AMlJo4.ttf
26 ms
5FbdueAKJ1eeO4CsvGhNRevvDin1pK8aKteLpeZ5c0A.ttf
26 ms
1EqTbJWOZQBfhZ0e3RL9uvesZW2xOQ-xsNqO47m55DA.ttf
24 ms
MZ1aViPqjfvZwVD_tzjjkwLUuEpTyoUstqEm5AMlJo4.ttf
23 ms
jZjuDZSb58pQtWhOr6q-6ALUuEpTyoUstqEm5AMlJo4.ttf
25 ms
firehist.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Document doesn't have a <title> element
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
firehist.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
firehist.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Firehist.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Firehist.org 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.
firehist.org
Open Graph description is not detected on the main page of Firehist. 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: