2 sec in total
77 ms
1.7 sec
216 ms
Click here to check amazing Yaskawa content for United States. Otherwise, check out these important facts you probably never knew about yaskawa.com
Yaskawa is the leading global manufacturer of low and medium voltage variable frequency drives, servo systems, machine controllers and industrial robots.
Visit yaskawa.comWe analyzed Yaskawa.com page load time and found that the first response time was 77 ms and then it took 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.
yaskawa.com performance score
name
value
score
weighting
Value6.9 s
1/100
10%
Value12.6 s
0/100
25%
Value8.0 s
22/100
10%
Value1,030 ms
26/100
30%
Value0.042
99/100
15%
Value14.5 s
9/100
10%
77 ms
556 ms
78 ms
194 ms
45 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 89% of them (82 requests) were addressed to the original Yaskawa.com, 3% (3 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (556 ms) belongs to the original domain Yaskawa.com.
Page size can be reduced by 323.1 kB (29%)
1.1 MB
775.2 kB
In fact, the total size of Yaskawa.com 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 418.4 kB which makes up the majority of the site volume.
Potential reduce by 316.7 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 316.7 kB or 88% of the original size.
Potential reduce by 5.9 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. Yaskawa images are well optimized though.
Potential reduce by 402 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 52 (60%)
86
34
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yaskawa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
yaskawa.com
77 ms
www.yaskawa.com
556 ms
js
78 ms
gtm.js
194 ms
css
45 ms
main.css
70 ms
combo
192 ms
clay.css
191 ms
main.css
118 ms
combo
117 ms
js_loader_config
115 ms
combo
187 ms
combo
273 ms
combo
281 ms
js_bundle_config
187 ms
combo
276 ms
main.css
316 ms
combo
277 ms
jquery-ui.min.css
276 ms
asBreadcrumbs.min.css
277 ms
swiperCSS.css
324 ms
swiperJS.js
369 ms
main.js
351 ms
surveyProd.js
348 ms
jquery-ui.min.js
394 ms
cookie.js
394 ms
menu_scroll_rating_mask_concated.js
394 ms
lightslider.js
392 ms
printPreview.js
392 ms
freeze-table.min.js
393 ms
jquery-asBreadcrumbs.min.js
408 ms
buttons.js
69 ms
loader.js
70 ms
custom.js
406 ms
prum.min.js
150 ms
b685457d-b580-4066-be13-ce9c5b340825
112 ms
47e6ef22-f1d7-4d83-85f5-5398bb553556
111 ms
6e73fea6-5598-41f1-8559-096720e623e9
110 ms
906ec977-d77d-4bd8-bb2c-dcc0331637e5
110 ms
80c7771f-7f26-4f95-9485-22814936a736
144 ms
3b43c9c6-782e-4a71-a14e-fe5247a501e4
145 ms
5e2c1c19-1df8-43bf-903b-c560f37ef920
145 ms
f78dd3ba-47db-4a2f-937f-0182f72d9def
144 ms
46dc5c1a-6a39-4bdd-81fe-4fb3fe6fa800
144 ms
37c64f2b-9348-4fac-9dda-342e16b79e9d
143 ms
76e68af0-9a8c-4487-8138-48832911730f
175 ms
11fd4ba5-c534-47fe-8bbf-5c92ddc97aaf
182 ms
layout_set_logo
178 ms
icon_Hemburger.svg
173 ms
icon_Location.svg
171 ms
activeLocation.svg
175 ms
icon_Search.svg
191 ms
help.png
216 ms
icon_Lookup.svg
216 ms
icon_User.svg
218 ms
Icon-arrow.svg
219 ms
0a115006-12a3-f4ea-539b-6a207a714916
219 ms
80dc3da2-c4dc-74c5-42d7-b42db2742c53
220 ms
a879dfb1-92f1-9e92-0474-a9b747abd1f9
224 ms
4998bc19-9907-f04a-0d3c-6a42ebd76c02
182 ms
5a9377dc-8a22-4e3d-8205-4a8e570d60a0
179 ms
ff8c0f44-fc47-ae87-f5d0-9741aa735993
193 ms
471f29ca-11ad-3043-faca-6a3217afdd38
140 ms
b03ffb8a-8e0e-26c5-baa7-4612e34ea601
148 ms
d08780d9-0b24-bace-6154-a525e37d89e4
152 ms
b239bd85-3aa8-aa2c-4d7d-4f23e30387a9
175 ms
604fceee-2100-0755-3bad-fafea2a7bdcd
175 ms
2a68fa58-d76d-3d53-7370-f112237fdedb
174 ms
330e19b3-9ee8-3ea5-1e45-c913f53e9920
175 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf
54 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xk.ttf
55 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf
62 ms
layout_set_logo.png
161 ms
6fe86930-24ed-5ce1-ee84-26f1f1282a56
194 ms
794d31f0-ef94-ad79-8c33-4e69b5a3c276
192 ms
b69e6c7f-8cf9-d465-5a29-2cac2331cbd9
191 ms
cdd5b20a-d5f0-d805-6c41-c2fcc6c5650d
192 ms
08b26dab-26df-ff66-1865-a7f8b05aedb3
165 ms
e4639be3-8741-4550-b794-a80e02d31b52
160 ms
ed3cae6b-dccb-4e6c-8240-8c28914c9bde
207 ms
0763b248-5939-4e92-ad16-11fc08b4997d
206 ms
dd99b9df-7237-2aa0-e12a-2a9f8645187d
206 ms
3e8f4818-c6de-4427-bf8f-b528fab4a9c3
206 ms
475621bd-ac2b-46dd-9350-3195bbd354db
201 ms
70560028-ffc6-4479-9781-f34c9f5e09bb
178 ms
30b7d5a3-866b-4690-a5cb-71ca2e5a102a
177 ms
2a5f38d2-4134-4442-abb0-ffc46aa94a95
175 ms
icons.svg
200 ms
stripe.png
171 ms
fontawesome-webfont.woff
50 ms
gateway.min.js
220 ms
38 ms
yaskawa.com 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
button, link, and menuitem elements do not have accessible names.
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
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
Image elements do not have [alt] attributes
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.
yaskawa.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
yaskawa.com 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
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yaskawa.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Yaskawa.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.
yaskawa.com
Open Graph description is not detected on the main page of Yaskawa. 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: