7.1 sec in total
1.5 sec
5.3 sec
278 ms
Click here to check amazing Ork content. Otherwise, check out these important facts you probably never knew about ork.co.jp
私ども大阪ラセン管工業は、1912年の創業以来、約一世紀にわたり 日本で初めてのフレキシブルチューブ・ベローズの専門メーカーとして、 国内はもとより、世界と共に発展し、最良な製品を生産し続けてきました。
Visit ork.co.jpWe analyzed Ork.co.jp page load time and found that the first response time was 1.5 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
ork.co.jp performance score
name
value
score
weighting
Value8.4 s
0/100
10%
Value12.3 s
0/100
25%
Value13.2 s
2/100
10%
Value0 ms
100/100
30%
Value0.026
100/100
15%
Value8.7 s
36/100
10%
1533 ms
308 ms
642 ms
496 ms
341 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 89% of them (49 requests) were addressed to the original Ork.co.jp, 4% (2 requests) were made to Fonts.googleapis.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Ork.co.jp.
Page size can be reduced by 382.2 kB (14%)
2.7 MB
2.3 MB
In fact, the total size of Ork.co.jp main page is 2.7 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. 55% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 14.8 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. This page needs HTML code to be minified as it can gain 2.2 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 14.8 kB or 78% of the original size.
Potential reduce by 82.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. Ork images are well optimized though.
Potential reduce by 205.6 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 205.6 kB or 70% of the original size.
Potential reduce by 79.0 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. Ork.co.jp needs all CSS files to be minified and compressed as it can save up to 79.0 kB or 85% of the original size.
Number of requests can be reduced by 31 (60%)
52
21
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ork. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.ork.co.jp
1533 ms
normalize.css
308 ms
style.css
642 ms
prettyPhoto.css
496 ms
grid.css
341 ms
colorstheme.css
347 ms
jquery-1.js
941 ms
modernizr.js
460 ms
superfish.js
508 ms
jquery_002.js
520 ms
jquery_007.js
769 ms
jquery.js
823 ms
jquery_009.js
676 ms
jquery_005.js
693 ms
swfobject.js
796 ms
jquery_004.js
1179 ms
jquery_006.js
865 ms
jquery_008.js
922 ms
audio.js
967 ms
jquery_010.js
984 ms
custom.js
1037 ms
comment-reply.js
1076 ms
english.js
1121 ms
init.js
1113 ms
css
24 ms
css
36 ms
logo.png
469 ms
mail.png
175 ms
arrow.gif
190 ms
loading.png
161 ms
slide1.jpg
824 ms
slide2.jpg
846 ms
slide3.jpg
1281 ms
slide4.jpg
1044 ms
slide5.jpg
942 ms
slide6.jpg
1086 ms
slide7.jpg
1153 ms
slide8.jpg
1352 ms
slide9.jpg
1508 ms
slide10.jpg
1565 ms
slide11.jpg
1397 ms
slide12.jpg
1812 ms
slide13.jpg
1919 ms
index_bg.jpg
1521 ms
box-title-tail.png
1554 ms
new-21-265x183.jpg
1695 ms
cate_bana.png
1690 ms
spacer.gif
1708 ms
marker-2.gif
1739 ms
marker-1.gif
1858 ms
footer-tail.gif
1883 ms
analytics.js
21 ms
Q_pTky3Sc3ubRibGToTAYjnFfol0SnfBMmbnmUK0fZM.ttf
28 ms
UyYrYy3ltEffJV9QueSi4UpeNX8RPf6i6WQfJWyCWEs.ttf
27 ms
collect
34 ms
ork.co.jp accessibility score
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 valid value for its [lang] attribute.
ork.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
ork.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
JA
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ork.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Ork.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.
ork.co.jp
Open Graph description is not detected on the main page of Ork. 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: