9.9 sec in total
1.5 sec
8.3 sec
106 ms
Click here to check amazing Legrand content for Japan. Otherwise, check out these important facts you probably never knew about legrand.jp
データにもとづく顧客理解を起点に、広告の最適化から,個客のこころを動かすサイト創りまで,トータルにサポートするクリエイティブパフォーマンスエージェンシー。
Visit legrand.jpWe analyzed Legrand.jp page load time and found that the first response time was 1.5 sec and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
legrand.jp performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value15.3 s
0/100
25%
Value13.9 s
1/100
10%
Value1,210 ms
20/100
30%
Value0.784
5/100
15%
Value15.7 s
6/100
10%
1528 ms
174 ms
345 ms
690 ms
517 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 50% of them (44 requests) were addressed to the original Legrand.jp, 16% (14 requests) were made to Use.typekit.net and 5% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Legrand.jp.
Page size can be reduced by 221.9 kB (20%)
1.1 MB
879.7 kB
In fact, the total size of Legrand.jp main page is 1.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. Javascripts take 608.3 kB which makes up the majority of the site volume.
Potential reduce by 41.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 41.4 kB or 76% of the original size.
Potential reduce by 9.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. Legrand images are well optimized though.
Potential reduce by 152.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 152.2 kB or 25% of the original size.
Potential reduce by 18.7 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. Legrand.jp needs all CSS files to be minified and compressed as it can save up to 18.7 kB or 32% of the original size.
Number of requests can be reduced by 51 (77%)
66
15
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Legrand. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
legrand.jp
1528 ms
jquery-ui.css
174 ms
select.css
345 ms
style.css
690 ms
gray.css
517 ms
flexslider.css
526 ms
style.min.css
588 ms
styles.css
587 ms
jquery.min.js
788 ms
jquery-migrate.min.js
688 ms
css
36 ms
css
52 ms
rxn1skd.js
64 ms
fonts.css
724 ms
regenerator-runtime.min.js
781 ms
wp-polyfill.min.js
782 ms
index.js
860 ms
cf7-google-analytics.min.js
860 ms
wpcf7-recaptcha-controls.js
879 ms
api.js
42 ms
pixel-cat.min.js
991 ms
video.js
990 ms
jquery.js
989 ms
jquery-ui.js
1498 ms
jquery.easing.min.js
1188 ms
jquery.gray.min.js
1188 ms
jquery.event.drag-2.2.js
1250 ms
scripts.js
1249 ms
jquery.flexslider.js
1250 ms
fbevents.js
34 ms
wp-emoji-release.min.js
612 ms
logo_black.svg
531 ms
event_90x90.jpg
643 ms
news_90x90.jpg
642 ms
blog_90x90.jpg
644 ms
gtm.js
91 ms
b-40.png
797 ms
gototop_arrow.svg
798 ms
d
16 ms
d
19 ms
d
25 ms
d
19 ms
d
37 ms
d
6 ms
d
10 ms
ElegantIcons.woff
985 ms
recaptcha__ja.js
66 ms
js
72 ms
js
66 ms
analytics.js
213 ms
destination
249 ms
bat.js
247 ms
lt.js
308 ms
collect
73 ms
collect
82 ms
37 ms
97107298.js
18 ms
err.gif
870 ms
97107298
76 ms
ga-audiences
15 ms
20 ms
clarity.js
17 ms
logo_black.svg
303 ms
wave.jpg
984 ms
DUX.png
179 ms
woman_letter.png
880 ms
slider_arrow_left.svg
203 ms
slider_arrow_right.svg
350 ms
gototop_arrow_wh_hover.png
398 ms
gototop_arrow_hover.svg
425 ms
conversion.js
673 ms
flexslider-icon.woff
1225 ms
d
16 ms
d
24 ms
d
16 ms
d
31 ms
d
8 ms
d
8 ms
collect
58 ms
collect
20 ms
p.gif
30 ms
collect
18 ms
collect
36 ms
conversion_async.js
1453 ms
flexslider-icon.ttf
961 ms
676 ms
flexslider-icon.svg
946 ms
c.gif
7 ms
legrand.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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
Form elements do not have associated labels
Links do not have a discernible name
legrand.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
legrand.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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Legrand.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 Legrand.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.
legrand.jp
Open Graph data is detected on the main page of Legrand. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: