7.8 sec in total
1.4 sec
5.6 sec
927 ms
Click here to check amazing PIHER content. Otherwise, check out these important facts you probably never knew about piher.jp
Piher is a Family company. More than 50 in Professional Clamping Tool Manufacture & Design. High Quality Clamping Solutions
Visit piher.jpWe analyzed Piher.jp page load time and found that the first response time was 1.4 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
piher.jp performance score
name
value
score
weighting
Value9.9 s
0/100
10%
Value10.8 s
0/100
25%
Value13.3 s
2/100
10%
Value1,390 ms
16/100
30%
Value0.424
22/100
15%
Value12.9 s
13/100
10%
1356 ms
710 ms
368 ms
373 ms
377 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Piher.jp, 3% (3 requests) were made to Google-analytics.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Piher.com.
Page size can be reduced by 712.6 kB (19%)
3.8 MB
3.1 MB
In fact, the total size of Piher.jp main page is 3.8 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. 65% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 74.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 21.4 kB, which is 25% 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 74.8 kB or 88% of the original size.
Potential reduce by 37.8 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. PIHER images are well optimized though.
Potential reduce by 318.1 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 318.1 kB or 72% of the original size.
Potential reduce by 281.9 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. Piher.jp needs all CSS files to be minified and compressed as it can save up to 281.9 kB or 84% of the original size.
Number of requests can be reduced by 53 (62%)
86
33
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PIHER. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 31 to 1 for CSS and as a result speed up the page load time.
www.piher.com
1356 ms
global.css
710 ms
highdpi.css
368 ms
responsive-tables.css
373 ms
uniform.default.css
377 ms
blocklanguages.css
379 ms
blockcontact.css
390 ms
blocksearch.css
487 ms
jquery.autocomplete.css
497 ms
blocktags.css
498 ms
blocktopmenu.css
502 ms
superfish-modified.css
515 ms
blockviewed.css
606 ms
homeslider.css
612 ms
jquery.bxslider.css
615 ms
product_list.css
745 ms
homefeatured.css
640 ms
hooks.css
736 ms
theme5.css
737 ms
font1.css
737 ms
pv_custom.css
768 ms
productvideoextraright.css
825 ms
jquery.fancybox.css
845 ms
tooltipster.bundle.min.css
847 ms
tooltipster.borderless.min.css
853 ms
lgcookieslaw_1_1.css
856 ms
front.css
1013 ms
boninstagramcarousel.css
937 ms
owl.carousel.css
956 ms
owl.theme.default.css
960 ms
jquery-1.11.0.min.js
1204 ms
jquery-migrate-1.2.1.min.js
971 ms
jquery.easing.js
1058 ms
tools.js
1196 ms
global.js
1080 ms
10-bootstrap.min.js
1091 ms
css
55 ms
15-jquery.total-storage.min.js
920 ms
15-jquery.uniform-modified.js
836 ms
jquery.autocomplete.js
849 ms
blocksearch.js
917 ms
hoverIntent.js
918 ms
superfish-modified.js
932 ms
blocktopmenu.js
861 ms
homeslider.js
852 ms
jquery.bxslider.js
851 ms
GoogleAnalyticActionLib.js
869 ms
jquery.fancybox.js
889 ms
tooltipster.bundle.min.js
837 ms
front.js
967 ms
owl.carousel.js
850 ms
owl.carousel-front.js
819 ms
index.js
750 ms
css
14 ms
analytics.js
462 ms
piher-logo-1446039171.jpg
392 ms
f5e9c08d96dff54db68642b5d479c9a5c15126d1_TCP-PIHER-Web-Front.jpg
713 ms
d944a279c48882e5b5b1648092e025bab3de5837_PRL400-Parallel-PIHER-Web-Front.jpg
780 ms
4c56c35bfc77a9421d4db03a8f29d2cff82b40a2_Piher-ARM+3-Multiprop.jpg
768 ms
4094a7eb060e28686b1397ead7d29862cd5349fa_Albaola-Piher-Clamps-01.jpg
1073 ms
multiprop-p3-arm.jpg
469 ms
maxipress-r---depth16cm.jpg
467 ms
multiclamp.jpg
551 ms
rectangular-steel-band.jpg
554 ms
multi-device-support-for-laser--cameras.jpg
658 ms
mod-f---depth12cm.jpg
677 ms
multi-props.jpg
779 ms
sample-1.jpg
924 ms
sample-2.jpg
834 ms
sample-3.jpg
889 ms
sample-4.jpg
898 ms
sample-5.jpg
905 ms
sample-6.jpg
958 ms
sample-7.jpg
1018 ms
sample-8.jpg
1031 ms
sample-9.jpg
1031 ms
sample-10.jpg
1187 ms
sample-11.jpg
1080 ms
sample-12.jpg
1139 ms
Logo-FEDER.png
1152 ms
43b3b032356574453b9483f64688b0a8f9df14a6_albaola-logo-130px.png
1153 ms
bx_loader.gif
809 ms
Piher-Fabrication-tag.png
818 ms
fontawesome-webfont.woff
891 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf
117 ms
NotoSans-Regular.ttf
1003 ms
ec.js
38 ms
collect
25 ms
collect
58 ms
ga-audiences
51 ms
piher.jp accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
piher.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
piher.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
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
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 doesn't use legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Piher.jp 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 Piher.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.
piher.jp
Open Graph description is not detected on the main page of PIHER. 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: