Tools & Wizards About Us
digicase.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

digicase.com

Contact Lens Case, Holder and Travel Kit - Digicase

Page Load Speed

10 sec in total

First Response

1.6 sec

Resources Loaded

8.2 sec

Page Rendered

210 ms

digicase.com screenshot

About Website

Click here to check amazing Digicase content. Otherwise, check out these important facts you probably never knew about digicase.com

The Digicase is perfect it's the perfect contact lens travel case, the automatic reminder that will alert you when it's time to change your contact lenses.

Visit digicase.com

Key Findings

We analyzed Digicase.com page load time and found that the first response time was 1.6 sec and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

digicase.com performance score

0

Network Requests Diagram

www.digicase.com

1599 ms

style.css

353 ms

wpsc-marketplace.css

1276 ms

compatibility.css

175 ms

styles.css

182 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 70% of them (64 requests) were addressed to the original Digicase.com, 3% (3 requests) were made to W.sharethis.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Digicase.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 839.0 kB (51%)

Content Size

1.6 MB

After Optimization

794.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Digicase.com main page is 1.6 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. 45% of websites need less resources to load. Javascripts take 867.7 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 111.6 kB

  • Original 138.9 kB
  • After minification 131.1 kB
  • After compression 27.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 111.6 kB or 80% of the original size.

Image Optimization

-4%

Potential reduce by 23.9 kB

  • Original 532.8 kB
  • After minification 508.8 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. Digicase images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 625.8 kB

  • Original 867.7 kB
  • After minification 860.0 kB
  • After compression 241.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 625.8 kB or 72% of the original size.

CSS Optimization

-82%

Potential reduce by 77.6 kB

  • Original 94.3 kB
  • After minification 81.1 kB
  • After compression 16.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. Digicase.com needs all CSS files to be minified and compressed as it can save up to 77.6 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

85

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Digicase. 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 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.digicase.com

www.digicase.com

1599 ms

style.css

style.css

353 ms

wpsc-marketplace.css

wpsc-marketplace.css

1276 ms

compatibility.css

compatibility.css

175 ms

styles.css

styles.css

182 ms

diggdigg-style.css

diggdigg-style.css

185 ms

easingslider.min.css

easingslider.min.css

266 ms

pagenavi-css.css

pagenavi-css.css

277 ms

swfobject.js

swfobject.js

329 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

556 ms

wp-e-commerce.js

wp-e-commerce.js

1902 ms

jquery.livequery.js

jquery.livequery.js

334 ms

user.js

user.js

364 ms

cufon-yui.js

cufon-yui.js

393 ms

Tahoma_400-Tahoma_700.font.js

Tahoma_400-Tahoma_700.font.js

698 ms

Verdana_400-Verdana_700.font.js

Verdana_400-Verdana_700.font.js

940 ms

jquery.cycle.all.min.js

jquery.cycle.all.min.js

480 ms

dropdown.js

dropdown.js

569 ms

jquery.easingslider.min.js

jquery.easingslider.min.js

611 ms

responsive.css

responsive.css

672 ms

form.css

form.css

720 ms

paypal-button-minicart.min.js

paypal-button-minicart.min.js

2532 ms

pinit.js

pinit.js

48 ms

buttons.js

buttons.js

5 ms

comment-reply.min.js

comment-reply.min.js

767 ms

jquery.form.min.js

jquery.form.min.js

778 ms

scripts.js

scripts.js

875 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

683 ms

bg_maincontainer.png

bg_maincontainer.png

126 ms

logo_sm.png

logo_sm.png

127 ms

lineborder_topmenu.png

lineborder_topmenu.png

125 ms

sqr_05.png

sqr_05.png

179 ms

more_03.png

more_03.png

178 ms

loading.gif

loading.gif

579 ms

digital_contact_lens_case_22.png

digital_contact_lens_case_22.png

1864 ms

digital_contact_lens_case_33.png

digital_contact_lens_case_33.png

1941 ms

digital_contact_lens_case_42.png

digital_contact_lens_case_42.png

2047 ms

digital_contact_lens_case_12.png

digital_contact_lens_case_12.png

2085 ms

nav-arrow-next.png

nav-arrow-next.png

1816 ms

nav-arrow-prev.png

nav-arrow-prev.png

1838 ms

bg_mainmenu.png

bg_mainmenu.png

1914 ms

middle-sep_03.png

middle-sep_03.png

1926 ms

icon_cart.png

icon_cart.png

1965 ms

c_main_linebottom.gif

c_main_linebottom.gif

2016 ms

c_main_linetop.gif

c_main_linetop.gif

2017 ms

c_main_lineleft.gif

c_main_lineleft.gif

2027 ms

c_main_lineright.gif

c_main_lineright.gif

2052 ms

c_main_tl.gif

c_main_tl.gif

2099 ms

c_main_tr.gif

c_main_tr.gif

2102 ms

c_main_bl.gif

c_main_bl.gif

2124 ms

c_main_br.gif

c_main_br.gif

2133 ms

digital_contact_lens_case_33-200x120.png

digital_contact_lens_case_33-200x120.png

2164 ms

indicator.gif

indicator.gif

2183 ms

digital_contact_lens_case_12-200x120.png

digital_contact_lens_case_12-200x120.png

2349 ms

digital_contact_lens_case_22-200x120.png

digital_contact_lens_case_22-200x120.png

2284 ms

digital_contact_lens_case_42-200x120.png

digital_contact_lens_case_42-200x120.png

2328 ms

payment_by_200x37.png

payment_by_200x37.png

2239 ms

monsterpay_logo.png

monsterpay_logo.png

2265 ms

paypalexpress.png

paypalexpress.png

2278 ms

2_Takealot.jpg

2_Takealot.jpg

2357 ms

image-200x120.jpeg

image-200x120.jpeg

2366 ms

bg_sidebox_m.gif

bg_sidebox_m.gif

2353 ms

bg_sidebox_t.gif

bg_sidebox_t.gif

2360 ms

bg_sidebox_b.gif

bg_sidebox_b.gif

2404 ms

ga.js

ga.js

92 ms

getAllAppDefault.esi

getAllAppDefault.esi

115 ms

like.php

like.php

101 ms

bg_bottomcontainer.gif

bg_bottomcontainer.gif

2313 ms

nav-icon-inactive.png

nav-icon-inactive.png

2323 ms

pinit_main.js

pinit_main.js

99 ms

__utm.gif

__utm.gif

13 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

304 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

343 ms

count.json

count.json

62 ms

getSegment.php

getSegment.php

153 ms

checkOAuth.esi

checkOAuth.esi

29 ms

t.dhj

t.dhj

8 ms

t.dhj

t.dhj

12 ms

cm

cm

37 ms

x35248

x35248

131 ms

s-3271.xgi

s-3271.xgi

12 ms

hbpix

hbpix

30 ms

11 ms

45 ms

pixel

pixel

21 ms

xrefid.xgi

xrefid.xgi

7 ms

pixel

pixel

17 ms

2981

2981

35 ms

index.a8fc48294ca4cc10eb440189d9f22d7c.html

index.a8fc48294ca4cc10eb440189d9f22d7c.html

18 ms

buttons.ab966a004186897711de4a5ed256c924.css

buttons.ab966a004186897711de4a5ed256c924.css

13 ms

st.125da8bfe70ad3e00a35a6e4c65d8bc5.js

st.125da8bfe70ad3e00a35a6e4c65d8bc5.js

4 ms

SEO Factors

digicase.com SEO score

0

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 Digicase.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 Digicase.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

digicase.com

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