9.9 sec in total
1.2 sec
8.3 sec
365 ms
Visit vdl.co.jp now to see the best up-to-date Vdl content for Japan and also check out these interesting facts you probably never knew about vdl.co.jp
デジタルフォントの開発・販売:視覚デザイン研究所(VDL)のオフィシャルサイト。VDL TYPE LIBRARY<デザイナーズフォント>は、美しい文字デザインによる日本語フォント=斬新なオリジナルフォントです。TV用フォントも揃っています。
Visit vdl.co.jpWe analyzed Vdl.co.jp page load time and found that the first response time was 1.2 sec and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
vdl.co.jp performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value14.7 s
0/100
25%
Value12.9 s
2/100
10%
Value1,140 ms
22/100
30%
Value0.317
36/100
15%
Value22.9 s
1/100
10%
1222 ms
513 ms
355 ms
1473 ms
558 ms
Our browser made a total of 180 requests to load all elements on the main page. We found that all of those requests were addressed to Vdl.co.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Vdl.co.jp.
Page size can be reduced by 511.9 kB (39%)
1.3 MB
801.9 kB
In fact, the total size of Vdl.co.jp 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. 70% of websites need less resources to load. Images take 782.6 kB which makes up the majority of the site volume.
Potential reduce by 73.0 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 73.0 kB or 90% of the original size.
Potential reduce by 56.1 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. Vdl images are well optimized though.
Potential reduce by 224.4 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 224.4 kB or 83% of the original size.
Potential reduce by 158.4 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. Vdl.co.jp needs all CSS files to be minified and compressed as it can save up to 158.4 kB or 88% of the original size.
Number of requests can be reduced by 9 (5%)
179
170
The browser has sent 179 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vdl. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
vdl.co.jp
1222 ms
generic.css
513 ms
headandfoot.css
355 ms
utility.css
1473 ms
top.css
558 ms
jquery-1.8.0.js
1739 ms
smartRollover.js
530 ms
acordion.js
683 ms
popimage.js
707 ms
swfobject.js
743 ms
smooth.pack.js
845 ms
top.js
854 ms
vdllogo.gif
172 ms
top_flash3thin.png
195 ms
try.gif
342 ms
samplefont.png
353 ms
top-fontnavi.gif
187 ms
logona-EL.gif
186 ms
logona-L.gif
341 ms
logona-R.gif
370 ms
logona-M.gif
374 ms
logona-DB.gif
387 ms
logona-B.gif
512 ms
logona-H.gif
512 ms
logona-U.gif
529 ms
logog-EL.gif
555 ms
logog-L.gif
560 ms
logog-R.gif
579 ms
logog-M.gif
682 ms
logog-DB.gif
683 ms
logog-B.gif
703 ms
logog-H.gif
737 ms
logog-U.gif
746 ms
logogblack.gif
772 ms
logomaru-EL.gif
850 ms
logomaru-L.gif
852 ms
logomaru-R.gif
879 ms
logomaru-M.gif
921 ms
logomaru-DB.gif
931 ms
logomaru-B.gif
963 ms
logomaru-H.gif
1020 ms
logomaru-U.gif
1021 ms
logojr-EL.gif
1054 ms
logojr-L.gif
1104 ms
logojr-R.gif
1116 ms
logojr-M.gif
1155 ms
logojr-DB.gif
1189 ms
logojr-B.gif
1108 ms
logojr-H.gif
1067 ms
logojr-U.gif
1110 ms
logojrblack.gif
1122 ms
logomarujr-EL.gif
1164 ms
logomarujr-L.gif
1025 ms
logomarujr-M.gif
1029 ms
logomarujr-DB.gif
1063 ms
logomarujr-B.gif
1108 ms
logomarujr-H.gif
1121 ms
logomarujr-U.gif
1163 ms
megag-EL.gif
1023 ms
megag-L.gif
1027 ms
megag-R.gif
1060 ms
megag-M.gif
1108 ms
megag-DB.gif
1120 ms
megag-B.gif
1126 ms
megag-H.gif
1029 ms
megag-U.gif
1058 ms
megamaru-EL.gif
1061 ms
megamaru-L.gif
1109 ms
megamaru-R.gif
1118 ms
megamaru-M.gif
1104 ms
megamaru-DB.gif
1028 ms
megamaru-B.gif
1081 ms
megamaru-H.gif
1061 ms
megamaru-U.gif
1110 ms
lineg-EL.gif
1119 ms
lineg-L.gif
1081 ms
lineg-R.gif
1032 ms
lineg-M.gif
1104 ms
lineg-DB.gif
1060 ms
lineg-B.gif
1108 ms
lineg-H.gif
1098 ms
lineg-U.gif
1079 ms
linegr-EL.gif
1030 ms
linegr-L.gif
1100 ms
linegr-R.gif
1088 ms
linegr-M.gif
1108 ms
linegr-DB.gif
1083 ms
linegr-B.gif
1041 ms
linegr-H.gif
1060 ms
linegr-U.gif
1104 ms
gigag-L.gif
1103 ms
gigag-M.gif
1084 ms
gigag-B.gif
1074 ms
gigag-EB.gif
1050 ms
gigag-U.gif
1074 ms
gigamaru-L.gif
1102 ms
gigamaru-M.gif
1121 ms
gigamaru-B.gif
1069 ms
gigamaru-EB.gif
1058 ms
gigamaru-U.gif
1064 ms
gigajr-L.gif
1088 ms
gigajr-M.gif
1086 ms
gigajr-B.gif
1138 ms
gigajr-EB.gif
1055 ms
gigajr-U.gif
1043 ms
gigamarujr-L.gif
1078 ms
gigamarujr-M.gif
1104 ms
gigamarujr-B.gif
1068 ms
gigamarujr-EB.gif
1132 ms
gigamarujr-U.gif
1065 ms
admin-EL.gif
1031 ms
admin-L.gif
1086 ms
admin-R.gif
1117 ms
admin-M.gif
1061 ms
admin-DB.gif
1115 ms
admin-B.gif
1034 ms
admin-H.gif
1073 ms
admin-U.gif
1101 ms
yotag-L.gif
1120 ms
yotag-R.gif
1062 ms
yotag-M.gif
1163 ms
yotag-DB.gif
1120 ms
yotag-B.gif
1150 ms
terag-L.gif
1399 ms
terag-M.gif
1366 ms
terag-B.gif
1205 ms
terag-EB.gif
1179 ms
terag-U.gif
1347 ms
petag-M.gif
1306 ms
petag-B.gif
1469 ms
petag-EB.gif
1361 ms
petag-U.gif
1338 ms
kyosensya-R.gif
1688 ms
kyosensya-M.gif
1362 ms
kyosensya-DB.gif
1417 ms
kyosensya-B.gif
1404 ms
kyosensya-H.gif
1591 ms
kyosensya-U.gif
1400 ms
peng-L.gif
1376 ms
peng-M.gif
1432 ms
peng-B.gif
1452 ms
peng-EB.gif
1441 ms
penlady-L.gif
1477 ms
penlady-M.gif
1513 ms
penlady-B.gif
1474 ms
penlady-EB.gif
1483 ms
v7min-L.gif
1468 ms
v7min-M.gif
1434 ms
v7min-B.gif
1476 ms
v7min-EB.gif
1518 ms
v7min-U.gif
1490 ms
v7go-L.gif
1486 ms
v7go-M.gif
1446 ms
v7go-B.gif
1426 ms
v7go-EB.gif
1476 ms
v7go-U.gif
1520 ms
v7marugo-L.gif
1435 ms
v7marugo-M.gif
1401 ms
v7marugo-B.gif
1362 ms
v7marugo-EB.gif
1248 ms
v7marugo-U.gif
1323 ms
top_main_img_NewLib.jpg
1808 ms
logona_preview.png
1447 ms
btn_font_off.jpg
1212 ms
btn_pro_off.jpg
1199 ms
btn_ord_off.jpg
1130 ms
top_main_img_logoG.jpg
1950 ms
top_main_img_logojrblack.png
1203 ms
letter2.gif
1186 ms
NYTDC_logo.png
1139 ms
tdc2_8120.jpg
1414 ms
top_main_img_kyosensya2.jpg
1720 ms
kitemarks.png
1178 ms
btn_backtotop.gif
1144 ms
new.gif
1271 ms
bnr_dBook_off.png
1461 ms
tvleasefont_baner.gif
1363 ms
shop-s_off.png
1384 ms
old-pro_off.jpg
1346 ms
acco_arrow-.png
1414 ms
vdl.co.jp accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
vdl.co.jp 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
General
Impact
Issue
Detected JavaScript libraries
vdl.co.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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vdl.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Vdl.co.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.
vdl.co.jp
Open Graph description is not detected on the main page of Vdl. 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: