Tools & Wizards About Us
cellphonecase.com screenshot

Report Summary

  • 0

    Performance

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 0

    Best Practices

  • 92

    SEO

    Google-friendlier than
    75% of websites

cellphonecase.com

Page Load Speed

1.9 sec in total

First Response

606 ms

Resources Loaded

1.1 sec

Page Rendered

201 ms

cellphonecase.com screenshot

About Website

Welcome to cellphonecase.com homepage info - get ready to check Cellphonecase best content right away, or after learning these important things about cellphonecase.com

Browse through the most popular and trendy cell phone cover cases and accessories for your new Apple, Samsung, LG, HTC, Nokia, Alcatel, ZTE and other best-selling smart phone devices. You’ve found the...

Visit cellphonecase.com

Key Findings

We analyzed Cellphonecase.com page load time and found that the first response time was 606 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

cellphonecase.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.131

81/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

cellphonecase.com

606 ms

css

34 ms

css

46 ms

styles.css

57 ms

styles.css

119 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Cellphonecase.com, 48% (31 requests) were made to Cdn4.bigcommerce.com and 38% (25 requests) were made to Cdn3.bigcommerce.com. The less responsive or slowest element that took the longest time to load (606 ms) belongs to the original domain Cellphonecase.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 471.1 kB (23%)

Content Size

2.0 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cellphonecase.com main page is 2.0 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. 50% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 61.3 kB

  • Original 73.5 kB
  • After minification 69.3 kB
  • After compression 12.2 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 61.3 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 22.9 kB

  • Original 1.4 MB
  • After minification 1.4 MB

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. Cellphonecase images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 223.5 kB

  • Original 322.2 kB
  • After minification 262.2 kB
  • After compression 98.7 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 223.5 kB or 69% of the original size.

CSS Optimization

-83%

Potential reduce by 163.3 kB

  • Original 197.5 kB
  • After minification 150.7 kB
  • After compression 34.2 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. Cellphonecase.com needs all CSS files to be minified and compressed as it can save up to 163.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (59%)

Requests Now

64

After Optimization

26

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cellphonecase.com

cellphonecase.com

606 ms

css

css

34 ms

css

css

46 ms

styles.css

styles.css

57 ms

styles.css

styles.css

119 ms

iselector.css

iselector.css

54 ms

flexslider.css

flexslider.css

59 ms

slide-show.css

slide-show.css

57 ms

styles-slide-show.css

styles-slide-show.css

58 ms

social.css

social.css

73 ms

white.css

white.css

74 ms

grid.css

grid.css

75 ms

cloud-store.css

cloud-store.css

77 ms

product.attributes.css

product.attributes.css

79 ms

ui.all.css

ui.all.css

108 ms

product.quickview.css

product.quickview.css

91 ms

imodal.css

imodal.css

93 ms

store.css

store.css

95 ms

jquery.min.js

jquery.min.js

74 ms

menudrop.js

menudrop.js

47 ms

iselector.js

iselector.js

47 ms

jquery.flexslider.js

jquery.flexslider.js

64 ms

viewport.js

viewport.js

48 ms

common.js

common.js

66 ms

jquery.autobox.js

jquery.autobox.js

71 ms

init.js

init.js

64 ms

jquery.uniform.min.js

jquery.uniform.min.js

82 ms

main.js

main.js

66 ms

jquery-ui.min.js

jquery-ui.min.js

87 ms

quickview.js

quickview.js

93 ms

jquery.form.js

jquery.form.js

162 ms

imodal.js

imodal.js

107 ms

bc_pinstrumentation.min.js

bc_pinstrumentation.min.js

157 ms

jquery.bgiframe.min.js

jquery.bgiframe.min.js

158 ms

superfish.js

superfish.js

159 ms

visitor.js

visitor.js

162 ms

analytics.js

analytics.js

43 ms

analytics.min.js

analytics.min.js

150 ms

beacon_api.js

beacon_api.js

127 ms

counter.js

counter.js

16 ms

collect

collect

113 ms

t.php

t.php

163 ms

loader.png

loader.png

108 ms

cpc_logo_1423087611__00366.jpg

cpc_logo_1423087611__00366.jpg

65 ms

cell_phone_case_iphone_6s_phonecases_covers.jpg

cell_phone_case_iphone_6s_phonecases_covers.jpg

64 ms

samsung_galaxy_phone_covers_cell_phone_case.jpg

samsung_galaxy_phone_covers_cell_phone_case.jpg

140 ms

samsung_galaxy_note_5_cell_phone_case_27861__03176.jpg

samsung_galaxy_note_5_cell_phone_case_27861__03176.jpg

74 ms

motorola_moto_e_moto_x_moto_g_cell_phone_case_.jpg

motorola_moto_e_moto_x_moto_g_cell_phone_case_.jpg

142 ms

add-wishlist-inv.png

add-wishlist-inv.png

40 ms

Believe_Jesus_NOTE_5__16089.1438191770.330.500.jpg

Believe_Jesus_NOTE_5__16089.1438191770.330.500.jpg

125 ms

IcoRating0.png

IcoRating0.png

92 ms

SAM-NOTE4-PKZEBDIA-2__94227.1420591288.330.500.jpg

SAM-NOTE4-PKZEBDIA-2__94227.1420591288.330.500.jpg

123 ms

ZTE-ZMAX-BLKBLROBHLSTR-2__17325.1420593175.330.500.jpg

ZTE-ZMAX-BLKBLROBHLSTR-2__17325.1420593175.330.500.jpg

181 ms

England_Flag_NOTE_5__63439.1438191785.330.500.jpg

England_Flag_NOTE_5__63439.1438191785.330.500.jpg

144 ms

LGK10_HPCTUFFSO252_NP_1__13158.1458253298.330.500.jpg

LGK10_HPCTUFFSO252_NP_1__13158.1458253298.330.500.jpg

143 ms

LGK10_HPCTUFFSO271_NP_1__91572.1458253297.330.500.jpg

LGK10_HPCTUFFSO271_NP_1__91572.1458253297.330.500.jpg

146 ms

LGK10_HPCTUFFSO256_NP_1__61527.1458253297.330.500.jpg

LGK10_HPCTUFFSO256_NP_1__61527.1458253297.330.500.jpg

158 ms

LGK10_HPCTUFFSO255_NP_1__24566.1458253296.330.500.jpg

LGK10_HPCTUFFSO255_NP_1__24566.1458253296.330.500.jpg

160 ms

cart_empty.png

cart_empty.png

43 ms

icon_sprite.png

icon_sprite.png

40 ms

icon-search.png

icon-search.png

42 ms

header-bg.png

header-bg.png

38 ms

arrows-ffffff.png

arrows-ffffff.png

43 ms

fornax.min.js

fornax.min.js

46 ms

bg_direction_nav.png

bg_direction_nav.png

44 ms

Accessibility Review

cellphonecase.com accessibility score

68

Accessibility Issues

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

High

<frame> or <iframe> elements do not have a title

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

SEO Factors

cellphonecase.com SEO score

92

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cellphonecase.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Cellphonecase.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

cellphonecase.com

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