Tools & Wizards About Us
lawrencestorage.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

lawrencestorage.com

Self Storage in Lawrence, Kansas | Lawrence Storage

Page Load Speed

1.8 sec in total

First Response

43 ms

Resources Loaded

1.5 sec

Page Rendered

215 ms

lawrencestorage.com screenshot

About Website

Click here to check amazing Lawrence Storage content. Otherwise, check out these important facts you probably never knew about lawrencestorage.com

Lawrence Storage ensures safety is all in the details, from maintaining a well-lit and clean property to monitoring who comes and goes through our secure key code access gate. Great rates and no depos...

Visit lawrencestorage.com

Key Findings

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

Performance Metrics

lawrencestorage.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.067

97/100

15%

TTI (Time to Interactive)

Value8.2 s

41/100

10%

Network Requests Diagram

lawrencestorage.com

43 ms

lawrencestorage.com

555 ms

styles.css

143 ms

jquery.min.js

22 ms

987654321301015183

259 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 87% of them (26 requests) were addressed to the original Lawrencestorage.com, 3% (1 request) were made to Ajax.googleapis.com and 3% (1 request) were made to Birdeye.com. The less responsive or slowest element that took the longest time to load (555 ms) belongs to the original domain Lawrencestorage.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 9.9 kB (6%)

Content Size

160.8 kB

After Optimization

151.0 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Lawrencestorage.com main page is 160.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Javascripts take 137.6 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 8.1 kB

  • Original 11.2 kB
  • After minification 9.5 kB
  • After compression 3.1 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 1.7 kB, which is 15% 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 8.1 kB or 72% of the original size.

JavaScript Optimization

-0%

Potential reduce by 483 B

  • Original 137.6 kB
  • After minification 137.6 kB
  • After compression 137.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-11%

Potential reduce by 1.3 kB

  • Original 12.0 kB
  • After minification 12.0 kB
  • After compression 10.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. Lawrencestorage.com needs all CSS files to be minified and compressed as it can save up to 1.3 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (24%)

Requests Now

25

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lawrencestorage.com

lawrencestorage.com

43 ms

lawrencestorage.com

lawrencestorage.com

555 ms

styles.css

styles.css

143 ms

jquery.min.js

jquery.min.js

22 ms

987654321301015183

987654321301015183

259 ms

polyfills.min.js

polyfills.min.js

160 ms

velocity.min.js

velocity.min.js

156 ms

js

js

120 ms

richmarker-compiled.js

richmarker-compiled.js

155 ms

automatit_carousel.min.js

automatit_carousel.min.js

153 ms

scripts.js

scripts.js

153 ms

automatit_carousel.min.css

automatit_carousel.min.css

140 ms

987654321301015183

987654321301015183

256 ms

header_map_icon.svg

header_map_icon.svg

142 ms

ic_white_phone.svg

ic_white_phone.svg

143 ms

lawrence_logo.svg

lawrence_logo.svg

141 ms

home_phone_icon.svg

home_phone_icon.svg

159 ms

home_coded_icon.svg

home_coded_icon.svg

138 ms

home_onsite_icon.svg

home_onsite_icon.svg

142 ms

home_fullyfenced_icon.svg

home_fullyfenced_icon.svg

288 ms

home_contactless_icon.svg

home_contactless_icon.svg

296 ms

home_variety_icon.svg

home_variety_icon.svg

282 ms

home_well_lit_icon.svg

home_well_lit_icon.svg

288 ms

home_video_icon.svg

home_video_icon.svg

275 ms

home_insurance.svg

home_insurance.svg

292 ms

home_map_icon.svg

home_map_icon.svg

424 ms

home_officehours_icon.svg

home_officehours_icon.svg

419 ms

home_accesshours_icon.svg

home_accesshours_icon.svg

427 ms

home_cta_image.webp

home_cta_image.webp

427 ms

automatit_logo.svg

automatit_logo.svg

420 ms

Accessibility Review

lawrencestorage.com accessibility score

100

Accessibility Issues

Best Practices

lawrencestorage.com best practices score

75

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

lawrencestorage.com SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

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

lawrencestorage.com

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