2.6 sec in total
252 ms
1.7 sec
578 ms
Visit fontself.com now to see the best up-to-date Fontself content for Brazil and also check out these interesting facts you probably never knew about fontself.com
Create custom fonts in minutes with Fontself Maker, a powerful font maker easy to use and made for all creatives.
Visit fontself.comWe analyzed Fontself.com page load time and found that the first response time was 252 ms and then it took 2.3 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.
fontself.com performance score
name
value
score
weighting
Value2.6 s
62/100
10%
Value7.0 s
6/100
25%
Value3.5 s
87/100
10%
Value200 ms
89/100
30%
Value0.065
97/100
15%
Value8.4 s
39/100
10%
252 ms
41 ms
94 ms
75 ms
85 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fontself.com, 30% (24 requests) were made to V.fastcdn.co and 15% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (847 ms) relates to the external source Api.teletext.io.
Page size can be reduced by 802.5 kB (39%)
2.1 MB
1.3 MB
In fact, the total size of Fontself.com main page is 2.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. 70% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 130.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. 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 130.2 kB or 82% of the original size.
Potential reduce by 42.6 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. Fontself images are well optimized though.
Potential reduce by 228.7 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 228.7 kB or 54% of the original size.
Potential reduce by 401.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. Fontself.com needs all CSS files to be minified and compressed as it can save up to 401.0 kB or 83% of the original size.
Number of requests can be reduced by 27 (42%)
64
37
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fontself. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
www.fontself.com
252 ms
all.js
41 ms
css
94 ms
031a761e2b05d2bed213fd1f07412755.css
75 ms
a5cb880a745154a6a1a45f3465215dfd.js
85 ms
v0.js
85 ms
amp-youtube-0.1.js
400 ms
342 ms
gtm.js
418 ms
share-this-twitter-button.png
429 ms
index.html
500 ms
0sTQzbapM8j.js
435 ms
ping
324 ms
geo-ip
847 ms
visit
375 ms
18674811-0-Fontself-logotype32b.png
188 ms
11692398-0-9470548-0-FS-AI-CC-8.png
191 ms
11692263-0-9470538-0-FS-PS-CC-8.png
190 ms
11834373-0-blob.png
240 ms
11834328-0-AnyShape.png
244 ms
11834338-0-DragDrop.png
244 ms
11834343-0-Color.png
243 ms
11834333-0-ExportOTF.png
244 ms
20090161-0-Companies-logos-grey.png
243 ms
11692093-0-7669618-0-FS-Praises.png
286 ms
15654391-0-Screenshot-2017-04-1.png
304 ms
11692103-0-7908288-0-MadewithFo.jpg
305 ms
11691923-0-9601093-0-ABC-color-.png
321 ms
11691968-0-6100233-0-Adobe-Illu.png
298 ms
11691953-0-6103763-0-blob.png
299 ms
19622861-0-School-logos-greyed-.png
322 ms
11692618-0-11692098-0-6122543-0.jpg
351 ms
11692048-0-1849429-0-maker-revo.png
349 ms
11691998-0-1483962-0-KSbadgefun.png
357 ms
11692013-0-1849489-0-maker-font.png
357 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
260 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
315 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
371 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
372 ms
EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff
372 ms
PRmiXeptR36kaC0GEAetxh_xHqYgAV9Bl_ZQbYUxnQU.woff
371 ms
xjAJXh38I15wypJXxuGMBobN6UDyHWBl620a-IRfuBk.woff
400 ms
PRmiXeptR36kaC0GEAetxn5HxGBcBvicCpTp6spHfNo.woff
375 ms
PRmiXeptR36kaC0GEAetxjqR_3kx9_hJXbbyU8S6IN0.woff
431 ms
PRmiXeptR36kaC0GEAetxkCDe67GEgBv_HnyvHTfdew.woff
430 ms
like.php
192 ms
sddefault.jpg
205 ms
y7JUBCdgi0w
296 ms
ar06jNH3RX8
362 ms
sddefault.jpg
233 ms
analytics.js
188 ms
uwt.js
187 ms
conversion_async.js
201 ms
fbevents.js
51 ms
4qFiRLLPSF7.js
189 ms
lH1ibRl5GKq.png
215 ms
1003294793079211
89 ms
prototype.js
151 ms
jstorage.js
62 ms
32 ms
ec.js
47 ms
adsct
409 ms
172 ms
www-player-vflMqr8uC.css
101 ms
www-embed-player.js
98 ms
base.js
131 ms
collect
295 ms
237 ms
id
176 ms
YubHWiCUdycrt9r0pwxtCFMvWBBxMHmgtw0lFaZzSbY.js
170 ms
ad_status.js
264 ms
8K3Zg6NpZGSge3qWJUIO0OW0x1SCW4IXoAiImY1mvc4.js
168 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
29 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
32 ms
logo_ringo-vflOpz8ZI.png
125 ms
42 ms
loading_circle.svg
8 ms
qq1xivdq
39 ms
adsct
85 ms
shim.4a5a3d93.js
50 ms
fontself.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
fontself.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
fontself.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fontself.com 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 Fontself.com 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.
fontself.com
Open Graph data is detected on the main page of Fontself. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: