Tools & Wizards About Us
coinstarinc.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

coinstarinc.com

Creating a Better Everyday / Outerwall Inc.

Page Load Speed

3.3 sec in total

First Response

516 ms

Resources Loaded

2.6 sec

Page Rendered

233 ms

coinstarinc.com screenshot

About Website

Visit coinstarinc.com now to see the best up-to-date Coinstar Inc content and also check out these interesting facts you probably never knew about coinstarinc.com

Outerwall Inc. delivers retail products and services to consumers via self-service interactive kiosks.

Visit coinstarinc.com

Key Findings

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

Performance Metrics

coinstarinc.com performance score

0

Network Requests Diagram

outerwall.com

516 ms

lato.css

162 ms

global.css

507 ms

sidr.min.css

205 ms

jquery.bxslider.css

358 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Coinstarinc.com, 6% (4 requests) were made to W.sharethis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Outerwall.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 484.0 kB (34%)

Content Size

1.4 MB

After Optimization

924.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Coinstarinc.com main page is 1.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. 35% of websites need less resources to load. Images take 813.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 25.4 kB

  • Original 31.3 kB
  • After minification 25.4 kB
  • After compression 5.9 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. This page needs HTML code to be minified as it can gain 6.0 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 25.4 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 9.6 kB

  • Original 813.1 kB
  • After minification 803.5 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. Coinstar Inc images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 310.7 kB

  • Original 412.1 kB
  • After minification 385.8 kB
  • After compression 101.4 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 310.7 kB or 75% of the original size.

CSS Optimization

-91%

Potential reduce by 138.3 kB

  • Original 151.5 kB
  • After minification 66.7 kB
  • After compression 13.3 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. Coinstarinc.com needs all CSS files to be minified and compressed as it can save up to 138.3 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (53%)

Requests Now

59

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

outerwall.com

outerwall.com

516 ms

lato.css

lato.css

162 ms

global.css

global.css

507 ms

sidr.min.css

sidr.min.css

205 ms

jquery.bxslider.css

jquery.bxslider.css

358 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

8 ms

modernizr-custom.js

modernizr-custom.js

402 ms

analytics.js

analytics.js

8 ms

outerwall.min.js

outerwall.min.js

259 ms

jquery.bxslider.js

jquery.bxslider.js

386 ms

outerwall_home.js

outerwall_home.js

364 ms

buttons.js

buttons.js

6 ms

header_logo_2x.png

header_logo_2x.png

193 ms

mobile_menu_2x.png

mobile_menu_2x.png

134 ms

mobile-nav-close.png

mobile-nav-close.png

250 ms

home-banner-07.jpg

home-banner-07.jpg

476 ms

home-banner-02.jpg

home-banner-02.jpg

1381 ms

home-banner-04.jpg

home-banner-04.jpg

570 ms

home-banner-05.jpg

home-banner-05.jpg

1234 ms

home-banner-06.jpg

home-banner-06.jpg

874 ms

home-banner-09.jpg

home-banner-09.jpg

1185 ms

footer_logo_2x.png

footer_logo_2x.png

634 ms

facebook_2x.png

facebook_2x.png

132 ms

twitter_2x.png

twitter_2x.png

371 ms

linkedin_2x.png

linkedin_2x.png

438 ms

kiosk-redbox.png

kiosk-redbox.png

240 ms

kiosk-coinstar_2x.png

kiosk-coinstar_2x.png

395 ms

kiosk-ecoatm.png

kiosk-ecoatm.png

669 ms

phone-gazelle.png

phone-gazelle.png

309 ms

collect

collect

104 ms

kiosk-redbox-shadow.png

kiosk-redbox-shadow.png

341 ms

kiosk-coinstar-shadow.png

kiosk-coinstar-shadow.png

492 ms

kiosk-ecoatm-shadow.png

kiosk-ecoatm-shadow.png

491 ms

phone-gazelle-shadow.png

phone-gazelle-shadow.png

856 ms

bullet_c_off_2x.png

bullet_c_off_2x.png

477 ms

bullet_b_off_2x.png

bullet_b_off_2x.png

578 ms

bullet_n_off_2x.png

bullet_n_off_2x.png

554 ms

bullet_i_off_2x.png

bullet_i_off_2x.png

567 ms

bullet_j_off_2x.png

bullet_j_off_2x.png

579 ms

bullet_s_off_2x.png

bullet_s_off_2x.png

657 ms

lato-lig-webfont.woff

lato-lig-webfont.woff

685 ms

getAllAppDefault.esi

getAllAppDefault.esi

9 ms

bx_loader.gif

bx_loader.gif

571 ms

nav-utility.png

nav-utility.png

988 ms

getSegment.php

getSegment.php

10 ms

checkOAuth.esi

checkOAuth.esi

6 ms

t.dhj

t.dhj

6 ms

t.dhj

t.dhj

11 ms

cm

cm

22 ms

x35248

x35248

101 ms

s-3271.xgi

s-3271.xgi

8 ms

hbpix

hbpix

25 ms

5 ms

pixel

pixel

16 ms

xrefid.xgi

xrefid.xgi

6 ms

pixel

pixel

13 ms

8 ms

2981

2981

21 ms

lato-lig-webfont.ttf

lato-lig-webfont.ttf

203 ms

index.2d85e55d89f85ae69e4f2ca5ab9438b7.html

index.2d85e55d89f85ae69e4f2ca5ab9438b7.html

15 ms

buttons.ab966a004186897711de4a5ed256c924.css

buttons.ab966a004186897711de4a5ed256c924.css

9 ms

stcommon.2b05accc08f1ee42fe1983647ab923ea.js

stcommon.2b05accc08f1ee42fe1983647ab923ea.js

3 ms

st.1188278743c14064d5e8ae56c8ada29c.js

st.1188278743c14064d5e8ae56c8ada29c.js

6 ms

SEO Factors

coinstarinc.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

coinstarinc.com

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