2.9 sec in total
541 ms
2 sec
350 ms
Click here to check amazing Uvex content for United States. Otherwise, check out these important facts you probably never knew about uvex.com
Visit uvex.comWe analyzed Uvex.com page load time and found that the first response time was 541 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
uvex.com performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value4.0 s
50/100
25%
Value3.9 s
82/100
10%
Value30 ms
100/100
30%
Value0
100/100
15%
Value4.0 s
88/100
10%
541 ms
94 ms
186 ms
184 ms
190 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 51% of them (26 requests) were addressed to the original Uvex.com, 22% (11 requests) were made to Static.xx.fbcdn.net and 8% (4 requests) were made to Etracker.de. The less responsive or slowest element that took the longest time to load (541 ms) belongs to the original domain Uvex.com.
Page size can be reduced by 430.4 kB (44%)
967.7 kB
537.3 kB
In fact, the total size of Uvex.com main page is 967.7 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. 45% of websites need less resources to load. Javascripts take 568.1 kB which makes up the majority of the site volume.
Potential reduce by 42.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 42.8 kB or 72% of the original size.
Potential reduce by 18.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. Uvex images are well optimized though.
Potential reduce by 327.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 327.2 kB or 58% of the original size.
Potential reduce by 42.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. Uvex.com needs all CSS files to be minified and compressed as it can save up to 42.0 kB or 87% of the original size.
Number of requests can be reduced by 24 (52%)
46
22
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Uvex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.uvex.com
541 ms
normalize.css
94 ms
main.css
186 ms
style.css
184 ms
modernizr-2.6.2.min.js
190 ms
e.js
232 ms
addthis_widget.js
10 ms
jquery.min.js
29 ms
purl.js
188 ms
plugins.js
209 ms
main.js
209 ms
jquery-1.8.3.min.js
388 ms
276 ms
t.js
257 ms
logo-uvex@2x.png
96 ms
world.png
285 ms
uvex_group.jpg
216 ms
uvex_safety.jpg
217 ms
uvex_sports.jpg
219 ms
uvex_sports_us.jpg
218 ms
uvex_honeywell.jpg
366 ms
about_us.png
285 ms
logo-fb-wintersports.png
285 ms
logo-fb-cycling.png
289 ms
logo-fb-equestrian.png
290 ms
logo-fb-safety.png
365 ms
logo-fb-sports.png
368 ms
UvexNHG-bold.woff
374 ms
UvexNHG-roman.woff
392 ms
UvexNHG-light.woff
391 ms
uvex-symbols.woff
370 ms
footer-bg-medium.jpg
358 ms
300lo.json
23 ms
like.php
139 ms
like.php
170 ms
sh.8e5f85691f9aaa082472a194.html
39 ms
like.php
132 ms
like.php
155 ms
qeKvIRsJabD.js
310 ms
LVx-xkvaJ0b.png
230 ms
cnt_js.php
259 ms
cntcc
260 ms
f1b0EAiQ-wg.css
193 ms
RJJsRWCWmtW.css
190 ms
AdP_CKHZFBh.css
189 ms
q68gy-v_YMF.js
265 ms
DFmZn3_ZO2h.js
228 ms
mfqI3d6rUg1.js
308 ms
_Qp3v7kqEMi.js
318 ms
Bw8qRoQ9D-v.js
41 ms
4ylGxU24Rah.js
158 ms
uvex.com accessibility score
uvex.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
uvex.com SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uvex.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Uvex.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.
uvex.com
Open Graph description is not detected on the main page of Uvex. 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: