2.9 sec in total
723 ms
2 sec
162 ms
Welcome to font.websozai.jp homepage info - get ready to check FONT Websozai best content for Japan right away, or after learning these important things about font.websozai.jp
フリーフォントの「超極細ゴシック体」書体。Extra Light(極細)よりも細いExtra Thin(超極細)。〝史上最細〟のゴシック体を目指しました。印刷かすれ要注意。
Visit font.websozai.jpWe analyzed Font.websozai.jp page load time and found that the first response time was 723 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.
font.websozai.jp performance score
name
value
score
weighting
Value2.0 s
85/100
10%
Value6.9 s
6/100
25%
Value4.7 s
69/100
10%
Value1,160 ms
22/100
30%
Value0.062
97/100
15%
Value10.2 s
25/100
10%
723 ms
453 ms
63 ms
27 ms
683 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 10% of them (6 requests) were addressed to the original Font.websozai.jp, 10% (6 requests) were made to C.betrad.com and 7% (4 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (979 ms) belongs to the original domain Font.websozai.jp.
Page size can be reduced by 198.4 kB (39%)
506.4 kB
308.0 kB
In fact, the total size of Font.websozai.jp main page is 506.4 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. 55% of websites need less resources to load. Images take 318.3 kB which makes up the majority of the site volume.
Potential reduce by 11.5 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 11.5 kB or 70% of the original size.
Potential reduce by 62.7 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, FONT Websozai needs image optimization as it can save up to 62.7 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 113.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 113.0 kB or 72% of the original size.
Potential reduce by 11.1 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. Font.websozai.jp needs all CSS files to be minified and compressed as it can save up to 11.1 kB or 74% of the original size.
Number of requests can be reduced by 35 (60%)
58
23
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FONT Websozai. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
font.websozai.jp
723 ms
style.css
453 ms
plusone.js
63 ms
adsbygoogle.js
27 ms
bookmark_button.js
683 ms
widgets.js
177 ms
all.js
27 ms
cb=gapi.loaded_0
20 ms
button-only@2x.png
391 ms
gkbs_1.png
391 ms
kfp1.png
783 ms
pr_f910_wide.png
979 ms
gkbs_2.png
663 ms
ca-pub-2364966780037480.js
54 ms
zrt_lookup.html
50 ms
show_ads_impl.js
62 ms
180 ms
btn.js
71 ms
xd_arbiter.php
64 ms
xd_arbiter.php
80 ms
ads
163 ms
osd.js
25 ms
button
24 ms
ads
185 ms
ads
237 ms
button.css
47 ms
shared.js
48 ms
button.js
51 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
141 ms
like.php
116 ms
pocket_button.png
3 ms
wy1X4hBW7e7.js
37 ms
LVx-xkvaJ0b.png
22 ms
0_9PdEccZL.jpg
139 ms
a.gif
31 ms
bcs0
65 ms
creative_add_on.js
142 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
60 ms
a.gif
5 ms
creative_add_on.js
109 ms
bcs0
4 ms
0_yOXfyb1q.jpg
155 ms
362 ms
surly.js
31 ms
jot
160 ms
dvtp_src.js
36 ms
ba.html
12 ms
4.gif
15 ms
2532.js
8 ms
box_19_top-right.png
12 ms
dvtp_src_internal26.js
17 ms
ci.png
5 ms
t2tv7.html
106 ms
visit.js
59 ms
avs581.js
10 ms
event.jpg
47 ms
reset.css
11 ms
entry-button.css
10 ms
bbtn-l_v3.png
4 ms
font.websozai.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
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
font.websozai.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
font.websozai.jp SEO score
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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Font.websozai.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Font.websozai.jp 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.websozai.jp
Open Graph description is not detected on the main page of FONT Websozai. 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: