5.9 sec in total
221 ms
5.4 sec
329 ms
Click here to check amazing WEH content. Otherwise, check out these important facts you probably never knew about weh.in
Quick Connectors (Quick Couplings, quick release couplings) for fluids and gases for leak testing, pressure testing, function testing and filling of fluids and gases; Refueling Components for Natural ...
Visit weh.inWe analyzed Weh.in page load time and found that the first response time was 221 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
weh.in performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value10.2 s
0/100
25%
Value13.0 s
2/100
10%
Value730 ms
41/100
30%
Value0.04
99/100
15%
Value10.4 s
24/100
10%
221 ms
2054 ms
40 ms
60 ms
18 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 96% of them (120 requests) were addressed to the original Weh.in, 2% (3 requests) were made to Stackpath.bootstrapcdn.com and 1% (1 request) were made to Weh.us. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Weh.in.
Page size can be reduced by 269.3 kB (16%)
1.7 MB
1.4 MB
In fact, the total size of Weh.in main page is 1.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. 75% 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. Images take 742.3 kB which makes up the majority of the site volume.
Potential reduce by 157.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. 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 157.8 kB or 86% of the original size.
Potential reduce by 47.4 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. WEH images are well optimized though.
Potential reduce by 36.9 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. This website has mostly compressed JavaScripts.
Potential reduce by 27.1 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. Weh.in needs all CSS files to be minified and compressed as it can save up to 27.1 kB or 21% of the original size.
Number of requests can be reduced by 78 (67%)
116
38
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WEH. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
weh.in
221 ms
www.weh.in
2054 ms
font-awesome.min.css
40 ms
bootstrap.min.css
60 ms
font-awesome.css
18 ms
fontawesome-all.min.js
48 ms
styles.css
31 ms
widgets.css
33 ms
em_cloudzoom.css
30 ms
em_variation.css
36 ms
lightbox.css
36 ms
FredSel.css
49 ms
social.css
44 ms
csslider.css
48 ms
owl.carousel.css
53 ms
style.css
51 ms
amshopby.css
94 ms
elasticsearch.css
92 ms
menu.css
92 ms
em_multidealpro.css
95 ms
settings.css
94 ms
captions.css
96 ms
videogallery.css
97 ms
cmspro.css
98 ms
styles.css
98 ms
qquoteadv.css
99 ms
qquoteadv_css.css
104 ms
tree.css
99 ms
distributors.css
105 ms
settings.css
100 ms
prototype.js
103 ms
ccard.js
117 ms
validation.js
119 ms
builder.js
117 ms
effects.js
118 ms
dragdrop.js
123 ms
controls.js
124 ms
slider.js
126 ms
js.js
125 ms
style.css
455 ms
theme.css.php
677 ms
form.js
120 ms
menu.js
105 ms
translate.js
104 ms
cookies.js
104 ms
jquery-1.8.3.min.js
102 ms
jquery-noconflict.js
100 ms
jquery.ba-hashchange.min.js
93 ms
jquery.hoverIntent.js
107 ms
jquery.touchwipe.min.js
104 ms
colorpicker.js
105 ms
lightbox.js
104 ms
bookmarks.js
104 ms
jquery-1.11.0.min.js
65 ms
jquery-migrate-1.2.1.min.js
74 ms
jquery.noconflict.js
76 ms
jquery.social.share.2.2.min.js
74 ms
ios-orientationchange-fix.js
76 ms
selectUl.js
76 ms
cloud-zoom.1.0.2.js
78 ms
variation_panel.js
75 ms
variation.js
76 ms
gala_opendeal.js
78 ms
adapt.js
76 ms
slide-up-down.js
77 ms
jquery-hover-effect.js
77 ms
hammer.js
65 ms
owl.carousel.js
64 ms
owl.carousel.min.js
65 ms
countdown.js
64 ms
em_multidealpro.js
61 ms
jquery.themepunch.plugins.min.js
62 ms
jquery.themepunch.revolution.min.js
60 ms
qquoteadv.js
60 ms
jquery.themepunch.tools.min.js
61 ms
jquery.themepunch.revolution.min.js
58 ms
menu.js
60 ms
csslider_1.1.js
59 ms
email-decode.min.js
56 ms
flaunt.js
58 ms
1200.css
15 ms
gtm.js
115 ms
logo.png
55 ms
dummy.png
54 ms
narrow-heading-bak.png
50 ms
Productline_Quick-Connectors_500x310.jpg
54 ms
image8.jpg
52 ms
Pic-01_Gruppe_H2_TK16_TK17_TSA1_TN1.jpg
53 ms
image6.jpg
62 ms
TW152_Sauerstoffabf_llung.jpg
62 ms
TK17_H2_35_MPa_High-Flow_Busse_LKWs.jpg
62 ms
Automatisierte_Pr_fungen_TW800.jpg
62 ms
comgine_images.png
57 ms
bkg-shadow.png
33 ms
icons.png
32 ms
Roboto-Regular-webfont.woff
596 ms
fontawesome-webfont.woff
748 ms
fontawesome-webfont.woff
28 ms
Roboto-Light-webfont.woff
603 ms
bkg-title-1.png
46 ms
footer-back.png
30 ms
flages.png
30 ms
yt_logo_rgb_light.png
30 ms
Roboto-Bold-webfont.woff
495 ms
930 ms
revolution.extension.video.min.js
89 ms
revolution.extension.slideanims.min.js
92 ms
revolution.extension.actions.min.js
93 ms
revolution.extension.layeranimation.min.js
94 ms
revolution.extension.navigation.min.js
97 ms
revolution.extension.parallax.min.js
99 ms
loading.gif
336 ms
automatisierung-standbild.jpg
38 ms
transparent.png
35 ms
ct_internal_thread.png
36 ms
ct_external_thread.png
37 ms
loader.gif
37 ms
ct_tube.png
20 ms
ct_beads.png
10 ms
ct_collars.png
12 ms
ct_swages-flares.png
25 ms
ct_barbs.png
12 ms
tk17_cng_black.jpg
18 ms
revicons.woff
379 ms
print.css
15 ms
weh.in 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.
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
weh.in 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
Missing source maps for large first-party JavaScript
weh.in 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
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weh.in 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 Weh.in 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.
weh.in
Open Graph description is not detected on the main page of WEH. 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: