Tools & Wizards About Us
storitz.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

storitz.com

Self-Storage Units - Best Price Guaranteed - Storitz.com

Page Load Speed

2.6 sec in total

First Response

161 ms

Resources Loaded

1.9 sec

Page Rendered

512 ms

storitz.com screenshot

About Website

Visit storitz.com now to see the best up-to-date Storitz content for United States and also check out these interesting facts you probably never knew about storitz.com

Find, compare and rent self storage units and mini storage near you. Storitz guarantees that you will get the best deal. It's the smartest way to shop for self storage anywhere in the U.S.

Visit storitz.com

Key Findings

We analyzed Storitz.com page load time and found that the first response time was 161 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.

Performance Metrics

storitz.com performance score

0

Network Requests Diagram

storitz.com

161 ms

www.storitz.com

329 ms

js

61 ms

tp.widget.sync.bootstrap.min.js

36 ms

css

82 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 38% of them (33 requests) were addressed to the original Storitz.com, 7% (6 requests) were made to Maps.googleapis.com and 6% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Storitz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 684.3 kB (17%)

Content Size

4.0 MB

After Optimization

3.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 24.6 kB

  • Original 32.9 kB
  • After minification 31.9 kB
  • After compression 8.3 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 24.6 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 25.0 kB

  • Original 3.0 MB
  • After minification 3.0 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. Storitz images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 491.3 kB

  • Original 743.4 kB
  • After minification 723.5 kB
  • After compression 252.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 491.3 kB or 66% of the original size.

CSS Optimization

-89%

Potential reduce by 143.5 kB

  • Original 160.8 kB
  • After minification 125.2 kB
  • After compression 17.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. Storitz.com needs all CSS files to be minified and compressed as it can save up to 143.5 kB or 89% of the original size.

Requests Breakdown

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

Requests Now

75

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

storitz.com

storitz.com

161 ms

www.storitz.com

www.storitz.com

329 ms

js

js

61 ms

tp.widget.sync.bootstrap.min.js

tp.widget.sync.bootstrap.min.js

36 ms

css

css

82 ms

auto_complete.css

auto_complete.css

130 ms

jquery-ui.css

jquery-ui.css

204 ms

animate.min.css

animate.min.css

207 ms

style.css

style.css

270 ms

zopim.js

zopim.js

139 ms

jquery.min.js

jquery.min.js

82 ms

jquery-ui.min.js

jquery-ui.min.js

103 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

37 ms

jquery.geocomplete.min.js

jquery.geocomplete.min.js

204 ms

infobox.min.js

infobox.min.js

197 ms

ny.application.js

ny.application.js

372 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

331 ms

buttons.js

buttons.js

26 ms

conversion.js

conversion.js

25 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

4 ms

9732.js

9732.js

23 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

96 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

96 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

125 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

125 ms

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

190 ms

fbevents.js

fbevents.js

193 ms

common.js

common.js

73 ms

util.js

util.js

78 ms

geocoder.js

geocoder.js

77 ms

ga.js

ga.js

142 ms

header-bg.png

header-bg.png

162 ms

storitz-bg-white.png

storitz-bg-white.png

162 ms

StorizLogo2015.png

StorizLogo2015.png

262 ms

phone-icon-home.png

phone-icon-home.png

162 ms

bedroom-hero.jpg

bedroom-hero.jpg

798 ms

closet-hero.jpg

closet-hero.jpg

1038 ms

desk-hero.jpg

desk-hero.jpg

1065 ms

living-room-hero.jpg

living-room-hero.jpg

999 ms

pattern-img.png

pattern-img.png

283 ms

self-storage-icons.png

self-storage-icons.png

380 ms

url-icon.png

url-icon.png

333 ms

9732.js

9732.js

107 ms

map-img.jpg

map-img.jpg

550 ms

Piles-of-Cash-img.jpg

Piles-of-Cash-img.jpg

468 ms

storageunit-img.jpg

storageunit-img.jpg

533 ms

nationwide-img.jpg

nationwide-img.jpg

722 ms

chicago-img.jpg

chicago-img.jpg

673 ms

dallas-img.jpg

dallas-img.jpg

800 ms

los-angeles-img.jpg

los-angeles-img.jpg

848 ms

Philadelphia-img.jpg

Philadelphia-img.jpg

822 ms

footer-bg.png

footer-bg.png

863 ms

footer-social-icons.png

footer-social-icons.png

886 ms

ytc.js

ytc.js

105 ms

195 ms

t.js

t.js

194 ms

controls.js

controls.js

82 ms

places_impl.js

places_impl.js

81 ms

getAllAppDefault.esi

getAllAppDefault.esi

175 ms

widget_v2.134.js

widget_v2.134.js

50 ms

__utm.gif

__utm.gif

108 ms

148 ms

t.js

t.js

101 ms

powered-by-google-on-white3.png

powered-by-google-on-white3.png

90 ms

autocomplete-icons.png

autocomplete-icons.png

45 ms

collect

collect

68 ms

80 ms

getSegment.php

getSegment.php

142 ms

checkOAuth.esi

checkOAuth.esi

14 ms

ga-audiences

ga-audiences

41 ms

s

s

8 ms

t.dhj

t.dhj

9 ms

t.dhj

t.dhj

16 ms

cm

cm

23 ms

s-3271.xgi

s-3271.xgi

16 ms

hbpix

hbpix

26 ms

9 ms

xrefid.xgi

xrefid.xgi

6 ms

pixel

pixel

19 ms

15 ms

2981

2981

28 ms

facebook_32.png

facebook_32.png

6 ms

mail-icon.png

mail-icon.png

364 ms

googleplus_32.png

googleplus_32.png

5 ms

twitter_32.png

twitter_32.png

5 ms

linkedin_32.png

linkedin_32.png

5 ms

SEO Factors

storitz.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Storitz.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 Storitz.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

storitz.com

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