5.7 sec in total
675 ms
4.6 sec
436 ms
Visit fujimimokei.com now to see the best up-to-date Fujimimokei content for Canada and also check out these interesting facts you probably never knew about fujimimokei.com
フジミ模型株式会社は静岡にある、自動車・航空機・艦艇・名城・建物などの模型を企画、製造、販売を行っている会社です。
Visit fujimimokei.comWe analyzed Fujimimokei.com page load time and found that the first response time was 675 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fujimimokei.com performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value14.6 s
0/100
25%
Value8.2 s
20/100
10%
Value140 ms
95/100
30%
Value0.821
4/100
15%
Value12.3 s
15/100
10%
675 ms
320 ms
336 ms
335 ms
339 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 97% of them (90 requests) were addressed to the original Fujimimokei.com, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Fujimimokei.com.
Page size can be reduced by 288.2 kB (11%)
2.5 MB
2.3 MB
In fact, the total size of Fujimimokei.com main page is 2.5 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 2.3 MB which makes up the majority of the site volume.
Potential reduce by 30.1 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 30.1 kB or 83% of the original size.
Potential reduce by 140.3 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. Fujimimokei images are well optimized though.
Potential reduce by 109.5 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 109.5 kB or 60% of the original size.
Potential reduce by 8.3 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. Fujimimokei.com needs all CSS files to be minified and compressed as it can save up to 8.3 kB or 75% of the original size.
Number of requests can be reduced by 35 (38%)
91
56
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fujimimokei. 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 as a result speed up the page load time.
fujimimokei.com
675 ms
reset.css
320 ms
global.css
336 ms
top.css
335 ms
common.js
339 ms
jquery-1.8.3.min.js
865 ms
jquery.easing.1.3.js
355 ms
jquery.carouFredSel-6.2.0-packed.js
796 ms
simplelib.min.js
500 ms
fujimi.js
501 ms
docLoading.js
506 ms
heightLine.js
531 ms
fixHeight.js
188 ms
%E3%82%B3%E3%82%99%E3%82%B7%E3%82%99%E3%83%A9%E3%83%8F%E3%82%99%E3%83%8A%E3%83%BC.jpg
1393 ms
loading.gif
183 ms
bgHeader.gif
184 ms
logo.gif
188 ms
btnMenu01_off.gif
185 ms
btnMenu02_off.gif
186 ms
btnMenu03_off.gif
315 ms
btnMenu04_off.gif
320 ms
btnMenu05_off.gif
336 ms
btnMeun06_off.gif
341 ms
bgCartMenu.gif
348 ms
btnLogin_off.gif
358 ms
btnCart_off.gif
482 ms
bgCartMenu2.gif
478 ms
btnLogout_off.jpg
501 ms
btnMypage_off.gif
511 ms
bgHeaderSearch.gif
520 ms
btnHeaderSearch.gif
534 ms
bgSlide.gif
637 ms
icoCar_off.gif
649 ms
icoBike_off.gif
666 ms
icoBoat_off.gif
679 ms
icoPlane_off.gif
692 ms
icoTrain_off.gif
713 ms
icoCastle_off.gif
795 ms
icoChara_off.gif
818 ms
icoTokusatsu_off.gif
833 ms
icoMilitary_off.gif
847 ms
icoKaigun_off.gif
866 ms
icoSeaWay_off.gif
890 ms
icoStructure_off.gif
954 ms
icoFinish_off.gif
983 ms
icoCatalog_off.gif
998 ms
chirashi_download.gif
1015 ms
catalog.jpg
2939 ms
%E3%83%96%E3%83%AD%E3%82%B02.jpg
1697 ms
%E5%90%8D%E7%A7%B0%E6%9C%AA%E8%A8%AD%E5%AE%9A-1.jpg
1215 ms
yahagi.jpg
1899 ms
%E7%B4%80%E4%BC%8A%E3%83%8F%E3%82%99%E3%83%8A%E3%83%BC.jpg
1286 ms
FUJIMISENDEN3.jpg
1916 ms
TOPkaga.jpg
2021 ms
shimakaze2.jpg
2184 ms
%E3%81%8F%E3%81%BE%E3%83%A2%E3%83%B3%E3%83%8F%E3%82%99%E3%83%8A%E3%83%BC.jpg
1693 ms
ga.js
29 ms
titleSearchNewItem.gif
1027 ms
__utm.gif
24 ms
shopapi.cgi
2173 ms
shopapi.cgi
2195 ms
4968728114729s-thumb-200x120-8598.jpg
1322 ms
collect
67 ms
iconYoyaku.gif
1008 ms
4968728114712s-thumb-200x120-8596.jpg
1418 ms
4968728114705s-thumb-200x120-8595.jpg
1345 ms
4968728114699s-thumb-200x120-8591.jpg
1692 ms
titleSearchRecommendItem.gif
1383 ms
4968728900254s-thumb-200x120-8516.jpg
1448 ms
4968728470146S-thumb-200x120-8554.jpg
1700 ms
4968728077031S-thumb-200x120-8552.jpg
1968 ms
4968728421988S-thumb-200x120-8550.jpg
1982 ms
4968728114750s-thumb-200x120-8528.jpg
1901 ms
4968728460024s-thumb-200x120-8522.jpg
2188 ms
daizas-thumb-200x120-8225.jpg
2006 ms
4968728091921.PT02s-thumb-200x120-8455.jpg
2317 ms
titleNews.gif
2023 ms
icoNews.gif
2014 ms
btnGoTop_off.gif
2038 ms
bgFooter.gif
2063 ms
lmFooterMenu.gif
2052 ms
lmSubMenu.gif
2168 ms
btnFooter01_off.gif
2147 ms
btnFooter02_off.gif
2166 ms
btnFooter03_off.gif
2091 ms
btnFooter08_off.gif
2169 ms
btnFooter07_off.gif
2174 ms
btnFooter04_off.gif
2176 ms
btnFooter05_off.gif
2181 ms
btnFooter06_off.gif
2166 ms
caution.gif
2167 ms
copy.gif
2162 ms
pager.gif
2174 ms
fujimimokei.com 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
Document doesn't have a <title> element
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.
fujimimokei.com 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
fujimimokei.com 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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fujimimokei.com 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 Fujimimokei.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.
fujimimokei.com
Open Graph description is not detected on the main page of Fujimimokei. 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: