Access lifeproof.com. OtterBox | Phone Cases, Screen Protection and Power

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

5/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value14.5 s

1/100

10%

TBT (Total Blocking Time)

Value10,370 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.105

88/100

15%

TTI (Time to Interactive)

Value36.9 s

0/100

10%

source

356 ms

plugins_with_jquery.js

14 ms

dwac-14.8.js

8 ms

lp_fonts.css

63 ms

frontend.min.css

26 ms

Our browser made a total of 137 requests to load all elements on the main page. We found that 9% of them (13 requests) were addressed to the original Lifeproof.com, 40% (55 requests) were made to Demandware.edgesuite.net and 10% (14 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (356 ms) belongs to the original domain Lifeproof.com.

Content Size

2.9 MB

After Optimization

1.5 MB

In fact, the total size of Lifeproof.com main page is 2.9 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. Javascripts take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 223.2 kB

Original 297.6 kB
After minification 277.3 kB
After compression 74.4 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 223.2 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 33.1 kB

Original 1.0 MB
After minification 983.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. Lifeproof images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 1.1 MB

Original 1.5 MB
After minification 1.4 MB
After compression 446.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 1.1 MB or 70% of the original size.

CSS Optimization

-80%

Potential reduce by 45.7 kB

Original 57.4 kB
After minification 56.4 kB
After compression 11.7 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.com needs all CSS files to be minified and compressed as it can save up to 45.7 kB or 80% of the original size.

Requests Now

126

After Optimization

The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lifeproof. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lifeproof.com 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.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.

Social Sharing Optimization

lifeproof.com

Open Graph description is not detected on the main page of Lifeproof. 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:

Report Summary

Performance

Accessibility

Best Practices

SEO

OtterBox | Phone Cases, Screen Protection and Power

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

source

plugins_with_jquery.js

dwac-14.8.js

lp_fonts.css

frontend.min.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

source

plugins_with_jquery.js

dwac-14.8.js

lp_fonts.css

frontend.min.css

device-selector.css

frontend.min.js

device-selector.min.js

picturefill.min.js

WebEvent.js

utag.sync.js

jquery.fancybox.min.js

jquery.cookie.js

jquery.fancybox.css

plugins_footer_no_delay.js

lifeproof.min.js

dwanalytics.js

gretel.min.js

lifeproof.css

id

target.js

36x70_ip6sP_front.jpg

null

iphone-6.png

iphone-6-plus.png

iphone-5-5s.png

iphone-5c.png

LP_iPad-Mini4_mktng_F-D_Black.png

ipad-mini.png

iPad_Air_2.png

ipad-air.png

FRE-Power-Respect.jpg

galaxy-s7.png

galaxy-s6.png

galaxy-s5.png

free-express_NAV.jpg

Moto-Droid-Turbo-2.png

1000x1000_LP_DroidMaxx2_resized.png

droid-turbo.png

lg-65.png

quickmount-accessories.png

belt-clip.png

armband.png