Tools & Wizards About Us
storageonterminal.com screenshot

Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

storageonterminal.com

Storguard | Storage on Terminal - Vancouver Storage

Page Load Speed

10.7 sec in total

First Response

4.8 sec

Resources Loaded

5.7 sec

Page Rendered

255 ms

storageonterminal.com screenshot

About Website

Visit storageonterminal.com now to see the best up-to-date Storage On Terminal content and also check out these interesting facts you probably never knew about storageonterminal.com

We offer convenient self storage lockers with no access fees or limitations. Locally owned and proud to keep a beautiful heritage building in our city.

Visit storageonterminal.com

Key Findings

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

Performance Metrics

storageonterminal.com performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

82/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.134

80/100

15%

TTI (Time to Interactive)

Value3.9 s

88/100

10%

Network Requests Diagram

storageonterminal.com

4769 ms

js

23 ms

style.css

105 ms

jquery.js

231 ms

jquery-migrate.min.js

114 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 45% of them (29 requests) were addressed to the original Storageonterminal.com, 23% (15 requests) were made to Maps.google.com and 16% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain Storageonterminal.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 582.7 kB (44%)

Content Size

1.3 MB

After Optimization

735.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Storageonterminal.com main page is 1.3 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. Javascripts take 651.7 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 32.6 kB

  • Original 39.8 kB
  • After minification 37.2 kB
  • After compression 7.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 32.6 kB or 82% of the original size.

Image Optimization

-18%

Potential reduce by 109.6 kB

  • Original 601.5 kB
  • After minification 491.9 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. Obviously, Storage On Terminal needs image optimization as it can save up to 109.6 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 419.1 kB

  • Original 651.7 kB
  • After minification 643.7 kB
  • After compression 232.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 419.1 kB or 64% of the original size.

CSS Optimization

-85%

Potential reduce by 21.4 kB

  • Original 25.3 kB
  • After minification 17.7 kB
  • After compression 3.9 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. Storageonterminal.com needs all CSS files to be minified and compressed as it can save up to 21.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (29%)

Requests Now

59

After Optimization

42

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

storageonterminal.com

storageonterminal.com

4769 ms

js

js

23 ms

style.css

style.css

105 ms

jquery.js

jquery.js

231 ms

jquery-migrate.min.js

jquery-migrate.min.js

114 ms

external-tracking.min.js

external-tracking.min.js

62 ms

mootools.v1.11.js

mootools.v1.11.js

121 ms

jd.gallery.js

jd.gallery.js

149 ms

jd.gallery.transitions.js

jd.gallery.transitions.js

104 ms

jd.gallery.css

jd.gallery.css

156 ms

analytics.js

analytics.js

44 ms

top-bar-tile-01.png

top-bar-tile-01.png

59 ms

storage-on-terminal.jpg

storage-on-terminal.jpg

77 ms

main-nav-line-01.jpg

main-nav-line-01.jpg

59 ms

main-nav-back-02.jpg

main-nav-back-02.jpg

61 ms

main-nav-back.jpg

main-nav-back.jpg

61 ms

home-feature-box.png

home-feature-box.png

213 ms

p1020857_2-570x348.jpg

p1020857_2-570x348.jpg

191 ms

thumbs_p1020857_2-570x348.jpg

thumbs_p1020857_2-570x348.jpg

127 ms

home_shapeimage_1fx.jpg

home_shapeimage_1fx.jpg

231 ms

thumbs_home_shapeimage_1fx.jpg

thumbs_home_shapeimage_1fx.jpg

115 ms

feature-item-01.jpg

feature-item-01.jpg

142 ms

feature-item-02.jpg

feature-item-02.jpg

181 ms

feature-item-03.jpg

feature-item-03.jpg

192 ms

icon-facebook.png

icon-facebook.png

187 ms

icon-twitter.png

icon-twitter.png

225 ms

footer-bar-tile-01.png

footer-bar-tile-01.png

196 ms

blog-box-home.png

blog-box-home.png

312 ms

date-back-box.png

date-back-box.png

209 ms

comment-back-box.png

comment-back-box.png

225 ms

collect

collect

12 ms

common.js

common.js

10 ms

map.js

map.js

9 ms

util.js

util.js

8 ms

marker.js

marker.js

8 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

102 ms

loading-bar-black.gif

loading-bar-black.gif

67 ms

onion.js

onion.js

26 ms

openhand_8_8.cur

openhand_8_8.cur

18 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

43 ms

stats.js

stats.js

14 ms

controls.js

controls.js

10 ms

transparent.png

transparent.png

16 ms

css

css

43 ms

spotlight-poi.png

spotlight-poi.png

30 ms

google4.png

google4.png

25 ms

mapcnt6.png

mapcnt6.png

26 ms

sv5.png

sv5.png

26 ms

tmapctrl.png

tmapctrl.png

17 ms

cb_scout5.png

cb_scout5.png

18 ms

tmapctrl4.png

tmapctrl4.png

17 ms

imgs8.png

imgs8.png

17 ms

vt

vt

27 ms

vt

vt

27 ms

vt

vt

28 ms

vt

vt

30 ms

vt

vt

34 ms

vt

vt

33 ms

vt

vt

53 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

6 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

11 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

11 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

11 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

67 ms

Accessibility Review

storageonterminal.com accessibility score

81

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

storageonterminal.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

storageonterminal.com SEO score

100

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

storageonterminal.com

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