2.9 sec in total
522 ms
2 sec
390 ms
Click here to check amazing Life Proof content for Hong Kong. Otherwise, check out these important facts you probably never knew about lifeproof.eu
LifeProof | OtterBox - EMEA
Visit lifeproof.euWe analyzed Lifeproof.eu page load time and found that the first response time was 522 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.
lifeproof.eu performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value16.7 s
0/100
25%
Value6.9 s
34/100
10%
Value1,140 ms
22/100
30%
Value0.096
91/100
15%
Value10.7 s
22/100
10%
522 ms
329 ms
150 ms
56 ms
217 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 17% of them (13 requests) were addressed to the original Lifeproof.eu, 60% (45 requests) were made to Demandware.edgesuite.net and 5% (4 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (720 ms) relates to the external source Demandware.edgesuite.net.
Page size can be reduced by 1.0 MB (42%)
2.4 MB
1.4 MB
In fact, the total size of Lifeproof.eu main page is 2.4 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. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 176.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 176.8 kB or 74% of the original size.
Potential reduce by 29.3 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. Life Proof images are well optimized though.
Potential reduce by 755.8 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 755.8 kB or 72% of the original size.
Potential reduce by 42.6 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. Lifeproof.eu needs all CSS files to be minified and compressed as it can save up to 42.6 kB or 81% of the original size.
Number of requests can be reduced by 22 (32%)
68
46
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Life Proof. 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 5 to 1 for CSS and as a result speed up the page load time.
source
522 ms
plugins_with_jquery.js
329 ms
dwac-14.8.js
150 ms
lp_fonts.css
56 ms
frontend.min.css
217 ms
frontend.min.js
216 ms
picturefill.min.js
33 ms
WebEvent.js
183 ms
utag.sync.js
185 ms
cookies.css
133 ms
global-drop-down-banner.css
187 ms
plugins_footer_no_delay.js
345 ms
lifeproof.min.js
417 ms
dwanalytics.js
321 ms
gretel.min.js
11 ms
id
20 ms
target.js
73 ms
lifeproof.css
30 ms
id
12 ms
ajax
386 ms
null
126 ms
iphone-6s.png
124 ms
iphone-6s-plus.png
126 ms
iphone-6.png
142 ms
iphone-6-plus.png
137 ms
iphone-5-5s.png
123 ms
iphone-5c.png
125 ms
ipad-air-2.png
206 ms
ipad-air.png
181 ms
ipad-mini.png
185 ms
ipad-2-3-4.png
187 ms
galaxy-s7.png
205 ms
galaxy-s6.png
215 ms
galaxy-s5.png
275 ms
galaxy-s4.png
277 ms
quickmount-accessories.png
272 ms
belt-clip.png
349 ms
armband.png
378 ms
lifejacket.png
390 ms
mounts.png
389 ms
ipad-accessories.png
389 ms
ipad-mini-accessories.png
390 ms
786x786_MOD61_FREpower.jpg
526 ms
385x385_MOD61_iPhone_6s_fre_grey.jpg
519 ms
385x385_MOD61_1_NUUDiP6.jpg
518 ms
385x385_MOD61_4_FRE_GS6.jpg
514 ms
385x385_MOD61_3_NUUDiP6Plus.jpg
516 ms
385x385_MOD61_6_NUUDiPadA2.jpg
516 ms
385x385_MOD61_5_iP5-5s.jpg
617 ms
FRE-homepage-video.jpg
658 ms
NUUD-homepage-video.jpg
659 ms
Power-homepage-video.jpg
720 ms
lifeactiv-homepage.jpg
720 ms
utag.js
364 ms
sprites.svg
111 ms
www.lifeproof.eu
135 ms
2E0F5C_4_0.woff
82 ms
motorbike-gs7-d.jpg
556 ms
6s-6sPlus-nuud-d.jpg
555 ms
lifeactiv-module50-d.jpg
576 ms
2.gif
14 ms
analytics.js
20 ms
iMAWebCookie.js
38 ms
activityi;src=5049308;type=ret01;cat=land01;ord=9039168721064.926
81 ms
utag.138.js
248 ms
utag.141.js
587 ms
collect
8 ms
collect
125 ms
null
52 ms
www.lifeproof.eu
134 ms
2E0F5C_0_0.woff
57 ms
2E0F5C_1_0.woff
163 ms
icons.woff
88 ms
s0578216821886
23 ms
__Analytics-Tracking
35 ms
lifeproof.eu accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
button, link, and menuitem elements do not have accessible names.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
[aria-*] attributes are not valid or misspelled
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
lifeproof.eu 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
lifeproof.eu 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lifeproof.eu 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 Lifeproof.eu 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.
lifeproof.eu
Open Graph description is not detected on the main page of Life Proof. 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: