Tools & Wizards About Us
nalex.co.jp screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    68% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

nalex.co.jp

超音波洗浄機・溶着機 設計 製作 | 日本アレックス株式会社

Page Load Speed

6.8 sec in total

First Response

1.4 sec

Resources Loaded

5.3 sec

Page Rendered

136 ms

nalex.co.jp screenshot

About Website

Visit nalex.co.jp now to see the best up-to-date Nalex content for Japan and also check out these interesting facts you probably never knew about nalex.co.jp

医療用・工業用の超音波洗浄機・超音波溶着機を設計製作しているメーカーです。自社でFEM解析に基づく振動子の設計から行っており、お客様のご要望に沿ったカスタマイズも承ります。

Visit nalex.co.jp

Key Findings

We analyzed Nalex.co.jp page load time and found that the first response time was 1.4 sec and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

nalex.co.jp performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.8 s

35/100

10%

Network Requests Diagram

www.nalex.co.jp

1417 ms

reset.css

395 ms

design.css

796 ms

format.css

609 ms

fonts.css

414 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 97% of them (32 requests) were addressed to the original Nalex.co.jp, 3% (1 request) were made to . The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Nalex.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 223.1 kB (43%)

Content Size

514.1 kB

After Optimization

291.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nalex.co.jp main page is 514.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Images take 195.5 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 19.6 kB

  • Original 25.1 kB
  • After minification 23.9 kB
  • After compression 5.5 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 19.6 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 1.9 kB

  • Original 195.5 kB
  • After minification 193.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. Nalex images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 108.1 kB

  • Original 162.3 kB
  • After minification 155.5 kB
  • After compression 54.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 108.1 kB or 67% of the original size.

CSS Optimization

-71%

Potential reduce by 93.5 kB

  • Original 131.2 kB
  • After minification 116.1 kB
  • After compression 37.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. Nalex.co.jp needs all CSS files to be minified and compressed as it can save up to 93.5 kB or 71% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (55%)

Requests Now

31

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nalex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.nalex.co.jp

www.nalex.co.jp

1417 ms

reset.css

reset.css

395 ms

design.css

design.css

796 ms

format.css

format.css

609 ms

fonts.css

fonts.css

414 ms

styles.css

styles.css

416 ms

style.css

style.css

956 ms

dashicons.min.css

dashicons.min.css

1351 ms

jquery.js

jquery.js

1746 ms

jquery-migrate.min.js

jquery-migrate.min.js

636 ms

hoverIntent.min.js

hoverIntent.min.js

632 ms

maxmegamenu.js

maxmegamenu.js

807 ms

wp-page-numbers.css

wp-page-numbers.css

822 ms

utility.js

utility.js

838 ms

jquery.form.min.js

jquery.form.min.js

773 ms

scripts.js

scripts.js

810 ms

jquery.sonar.min.js

jquery.sonar.min.js

829 ms

lazy-load.js

lazy-load.js

846 ms

script.php

script.php

1013 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

569 ms

logo.png

logo.png

195 ms

search.png

search.png

194 ms

main_image.jpg

main_image.jpg

1411 ms

products_btn.png

products_btn.png

230 ms

technology_btn.png

technology_btn.png

237 ms

company_btn.png

company_btn.png

447 ms

1x1.trans.gif

1x1.trans.gif

385 ms

logo_small.png

logo_small.png

385 ms

nalex-fonts.woff

nalex-fonts.woff

371 ms

42GGjxo0e8TfXWJDWAAAAAAFUhzzUAAA=

42GGjxo0e8TfXWJDWAAAAAAFUhzzUAAA=

2 ms

vs_img_top-200x160.jpg

vs_img_top-200x160.jpg

699 ms

infrastake_thumbnail-127x160.jpg

infrastake_thumbnail-127x160.jpg

519 ms

megapower_thumbnail-200x117.png

megapower_thumbnail-200x117.png

770 ms

Accessibility Review

nalex.co.jp accessibility score

83

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

nalex.co.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

nalex.co.jp SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nalex.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 Nalex.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.

Social Sharing Optimization

nalex.co.jp

Open Graph description is not detected on the main page of Nalex. 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: