1.7 sec in total
138 ms
1.2 sec
377 ms
Click here to check amazing Font content. Otherwise, check out these important facts you probably never knew about font.to
Visit font.toWe analyzed Font.to page load time and found that the first response time was 138 ms and then it took 1.6 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.
font.to performance score
138 ms
313 ms
10 ms
79 ms
151 ms
Our browser made a total of 27 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Font.to, 78% (21 requests) were made to Fontlab.com and 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (514 ms) relates to the external source Fontlab.com.
Page size can be reduced by 177.7 kB (14%)
1.3 MB
1.1 MB
In fact, the total size of Font.to main page is 1.3 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. 35% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 30.2 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 9.0 kB, which is 25% 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 30.2 kB or 85% of the original size.
Potential reduce by 115.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. Font 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.
Number of requests can be reduced by 11 (46%)
24
13
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Font. 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 4 to 1 for CSS and as a result speed up the page load time.
font.to
138 ms
index.php
313 ms
analytics.js
10 ms
normalize.css
79 ms
webflow.css
151 ms
fontlabfinal.webflow.css
141 ms
fontlab.style.css
140 ms
webfont.js
65 ms
jquery-2.1.0.min.js
211 ms
jquery-ui-1.10.4.custom.min.js
207 ms
plugins.js
155 ms
app.js
280 ms
webflow.js
285 ms
collect
43 ms
menu-ico-top.png
88 ms
fontlablogo.png
88 ms
_ico-2.png
270 ms
icon_fontlabstudio51_512x512_rgb.png
322 ms
_ico-1.png
332 ms
icon_typetool3_512.png
419 ms
icon_fontographer5_512x512_rgb.png
404 ms
icon_bitfonter3_512x512_rgb.png
459 ms
icon-otmaster-512.png
465 ms
icon_scanfont5_512x512_rgb.png
514 ms
plusone.js
64 ms
icons-fontastic.woff
315 ms
cb=gapi.loaded_0
4 ms
font.to best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
font.to 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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Font.to 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 Font.to 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.
font.to
Open Graph description is not detected on the main page of Font. 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: