22.1 sec in total
424 ms
11.4 sec
10.3 sec
Visit fonts.info now to see the best up-to-date Fonts content and also check out these interesting facts you probably never knew about fonts.info
An independent German type foundry
Visit fonts.infoWe analyzed Fonts.info page load time and found that the first response time was 424 ms and then it took 21.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
fonts.info performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value4.2 s
44/100
25%
Value4.4 s
74/100
10%
Value230 ms
86/100
30%
Value0.001
100/100
15%
Value4.5 s
82/100
10%
424 ms
1515 ms
599 ms
387 ms
296 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Fonts.info, 95% (36 requests) were made to Fdi-type.de and 3% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Google-analytics.com.
Page size can be reduced by 738.6 kB (65%)
1.1 MB
393.8 kB
In fact, the total size of Fonts.info 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. 45% of websites need less resources to load. Javascripts take 567.7 kB which makes up the majority of the site volume.
Potential reduce by 35.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. This page needs HTML code to be minified as it can gain 6.3 kB, which is 15% 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 35.6 kB or 81% of the original size.
Potential reduce by 54.8 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, Fonts needs image optimization as it can save up to 54.8 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 383.2 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 383.2 kB or 68% of the original size.
Potential reduce by 265.0 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. Fonts.info needs all CSS files to be minified and compressed as it can save up to 265.0 kB or 82% of the original size.
Number of requests can be reduced by 15 (42%)
36
21
The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fonts. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
fonts.info
424 ms
fdi-type.de
1515 ms
341e4a57816af3ba440d891ca87450ff_framework.css.d5d6b41a7980cc37a4e5eb50f47ceb33.css
599 ms
05e81b71abe4f22d6eb8d1a929494829_responsive.css.b276a6b9f0f3b35953c3b45201e4f0db.css
387 ms
90eb5adf50a8c640f633d47fd7eb1778_core.css.765fbf49debe135bb6cc8311ef83e9d6.css
296 ms
5a0da001ccc2200dc5625c3f3934497d_core_responsive.css.600de77c69026946d6c15d543511b4aa.css
300 ms
home.css.7eabe58507b3a424a8ad4ce1b98f5405.css
286 ms
b321f1ec40ca542bd93e573f541c5385_list.css.bd2fb1dc2571fc07886a6b13a50d3232.css
296 ms
97c0a48072ce601c9764cb6b00a6588a_page.css.bef71137898b795d5968e2ba7c56ae5f.css
376 ms
258adbb6e4f3e83cd3b355f84e3fa002_custom.css.5c0f0c2a4c32e40423006fe350cdc1d4.css
367 ms
root_library.js.018a9c44dfe9e91b06b504bad11ff461.js
1035 ms
root_js_lang_1.js.616d2b3d4f81fbbcc29a808d065e510c.js
538 ms
root_framework.js.f1b46c53138b311681b1094fa00e791a.js
1033 ms
global_global_core.js.b66f5983e013584169507d4d8efb31ff.js
444 ms
root_front.js.114ae3caa00d43c28823e91edd1ed326.js
1017 ms
responsivetabs.js.c98beb27194ef74681c5e80187f13a9b.js
1016 ms
front_app.js.98bdee6e839ad1ce2acd0b7c195fd274.js
1015 ms
root_map.js.0adc7318450db215344f222481435e36.js
1016 ms
fdilogo.svg
938 ms
canape.png.53e5372cff614404488b3b366d109fc8.png
1399 ms
elfen-aa.png.aba2803772f46a49ec131a735eaddd95.png
1385 ms
graublausans.png.ef68f9c8ba8a7ba929413d52d03ed2c7.png
1386 ms
gbslab-aa.png.314a45d92dd2c578417c3555e9f2c174.png
1376 ms
hooptie-aa.png.8e4f0377c4429e248563bbe9e3c97f49.png
1375 ms
iwan-aa.png.5d6ed7d4668f2182009ecff61cc537ce.png
1375 ms
logotypia-aa.png.f925e6bdacb6bab191503532233b7bc8.png
1375 ms
tierra-aa.png.a42859b5c3868d709075b6dc671b4886.png
1407 ms
uber-aa.png.c296d25ec8183a7a8670f00a8fcd6e98.png
1407 ms
wayfinding-aa.png.5403024346ba91ad56f7b009db7edd6e.png
1412 ms
www-aa.png.1f3d52cb87ba497fdd6da742f4394439.png
1412 ms
tguru.png
1412 ms
tinfo.png
1296 ms
llibrary.png
1296 ms
analytics.js
2023 ms
fontawesome-webfont.woff
778 ms
graublausans-extralight-webfont.woff
778 ms
icomoon.woff
771 ms
front_front_widgets.js.505b7df1702d0aea0f57725f6170f679.js
723 ms
fonts.info 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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
fonts.info best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
fonts.info SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fonts.info 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 Fonts.info 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.
fonts.info
Open Graph data is detected on the main page of Fonts. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: