5.8 sec in total
707 ms
4.8 sec
256 ms
Welcome to eiken-fp.co.jp homepage info - get ready to check Eiken Fp best content right away, or after learning these important things about eiken-fp.co.jp
株式会社栄建はFPの家など高性能注文住宅を施工する工務店です。名古屋・長久手・日進・瀬戸・尾張旭・豊田が施工エリアです。高気密・高断熱の省エネ住宅の、驚きの快適さをご体感ください。|名古屋・長久手・日進のFPの家・高断熱注文住宅
Visit eiken-fp.co.jpWe analyzed Eiken-fp.co.jp page load time and found that the first response time was 707 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
eiken-fp.co.jp performance score
name
value
score
weighting
Value8.2 s
0/100
10%
Value21.3 s
0/100
25%
Value16.0 s
0/100
10%
Value2,180 ms
6/100
30%
Value1.203
1/100
15%
Value73.9 s
0/100
10%
707 ms
311 ms
332 ms
333 ms
881 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 62% of them (54 requests) were addressed to the original Eiken-fp.co.jp, 16% (14 requests) were made to Scontent.xx.fbcdn.net and 11% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Eiken-fp.co.jp.
Page size can be reduced by 161.8 kB (12%)
1.4 MB
1.2 MB
In fact, the total size of Eiken-fp.co.jp main page is 1.4 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 13.4 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 13.4 kB or 70% of the original size.
Potential reduce by 42.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. Eiken Fp images are well optimized though.
Potential reduce by 95.2 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 95.2 kB or 55% of the original size.
Potential reduce by 10.6 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. Eiken-fp.co.jp needs all CSS files to be minified and compressed as it can save up to 10.6 kB or 79% of the original size.
Number of requests can be reduced by 25 (30%)
83
58
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eiken Fp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
eiken-fp.co.jp
707 ms
layout.css
311 ms
rollover.js
332 ms
dynamic.css
333 ms
jquery-1.js
881 ms
index.css
358 ms
mrliteLogger.js
846 ms
s_retargeting.js
565 ms
conversion.js
16 ms
dynamic.js
329 ms
logo.gif
314 ms
htxt.gif
319 ms
htel.gif
328 ms
hbtn.gif
333 ms
contact_h.jpg
338 ms
flash.jpg
1337 ms
tit1.jpg
644 ms
tit2.jpg
818 ms
event1.jpg
791 ms
event2.jpg
874 ms
event3.jpg
861 ms
event4.jpg
1290 ms
tit3.jpg
1099 ms
btn.jpg
1315 ms
btn2.jpg
1217 ms
btn3.jpg
1216 ms
btn13.jpg
1644 ms
btn4.jpg
1530 ms
btn6.jpg
1561 ms
btn7.jpg
1618 ms
btn8.jpg
1644 ms
btn9.jpg
1662 ms
btn10.jpg
1892 ms
btn11.jpg
1887 ms
btn12.jpg
1976 ms
img_b.jpg
2146 ms
tit_b.gif
1976 ms
img2_b.jpg
2155 ms
tit2_b.gif
2228 ms
img3_b.jpg
2431 ms
tit3_b.gif
2280 ms
img4_c.jpg
2470 ms
tit4_c.gif
2479 ms
img6_c.jpg
2681 ms
tit6_c.gif
2560 ms
img5_c.jpg
2718 ms
likebox.php
473 ms
mrliteLogger.php
337 ms
analytics.js
11 ms
86 ms
collect
19 ms
collect
60 ms
38 ms
ga-audiences
31 ms
tit5.gif
2484 ms
img9.jpg
2626 ms
tit7.gif
2468 ms
img7.jpg
2570 ms
tit8.gif
2702 ms
kyEKgjk51ZE.css
281 ms
xgj7bXhJNEH.css
350 ms
q68gy-v_YMF.js
484 ms
FJmpeSpHpjS.js
618 ms
0wM5s1Khldu.js
504 ms
1bNoFZUdlYZ.js
504 ms
img8.jpg
2438 ms
tit9.gif
2332 ms
f_award_c.jpg
2481 ms
culture.jpg
2530 ms
943808_958254337587322_5964777496207937938_n.png
873 ms
10411441_783164735096284_4583961921749199719_n.png
938 ms
224126_1519113997178_3363052_n.jpg
1065 ms
294526_160832324001472_374416940_n.jpg
1196 ms
944593_179321448891865_10264349_n.jpg
1104 ms
12507265_1096704723715735_516687868071300641_n.jpg
1074 ms
12400638_897465293694945_1310653769732219857_n.jpg
1073 ms
1467277_430472510386439_394938041_n.jpg
1072 ms
11050724_468562649959916_8544279747591917202_n.jpg
1132 ms
936161_463786667033168_712185121_n.jpg
1251 ms
10298901_318759474939890_1242773551205038774_n.jpg
1248 ms
9241_469851903123090_615302433_n.jpg
1141 ms
11002580_10153059403065688_7624280692616012510_n.jpg
1384 ms
12650830_176045436095440_5842024953814221207_n.jpg
1234 ms
wL6VQj7Ab77.png
70 ms
s7jcwEQH7Sx.png
68 ms
I6-MnjEovm5.js
69 ms
pQrUxxo5oQp.js
73 ms
eiken-fp.co.jp 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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
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.
eiken-fp.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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
eiken-fp.co.jp 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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Eiken-fp.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 Eiken-fp.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.
eiken-fp.co.jp
Open Graph description is not detected on the main page of Eiken Fp. 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: