Tools & Wizards About Us
lazarusvintage.com screenshot

Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

lazarusvintage.com

Lazarus Vintage MFG

Page Load Speed

13.1 sec in total

First Response

5.8 sec

Resources Loaded

6.9 sec

Page Rendered

371 ms

lazarusvintage.com screenshot

About Website

Welcome to lazarusvintage.com homepage info - get ready to check Lazarus Vintage best content for United States right away, or after learning these important things about lazarusvintage.com

Lazarus Vintage premium e-juice

Visit lazarusvintage.com

Key Findings

We analyzed Lazarusvintage.com page load time and found that the first response time was 5.8 sec and then it took 7.3 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

lazarusvintage.com performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value5.0 s

76/100

10%

Network Requests Diagram

lazarusvintage.com

5841 ms

f6b4fdc4bc4d3ecd4943b5748a8e64d4.css

46 ms

225901f16acf2d38f7ccdbdbb9767067.css

151 ms

ea71c5be30307048eebfb763cfe55db5.css

45 ms

prototype.js

126 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 79% of them (61 requests) were addressed to the original Lazarusvintage.com, 6% (5 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (5.8 sec) belongs to the original domain Lazarusvintage.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (71%)

Content Size

2.4 MB

After Optimization

693.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-86%

Potential reduce by 45.9 kB

  • Original 53.6 kB
  • After minification 44.1 kB
  • After compression 7.7 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 9.5 kB, which is 18% 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 45.9 kB or 86% of the original size.

Image Optimization

-5%

Potential reduce by 13.3 kB

  • Original 265.5 kB
  • After minification 252.2 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. Lazarus Vintage images are well optimized though.

JavaScript Optimization

-78%

Potential reduce by 1.3 MB

  • Original 1.7 MB
  • After minification 1.2 MB
  • After compression 365.5 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 1.3 MB or 78% of the original size.

CSS Optimization

-84%

Potential reduce by 368.6 kB

  • Original 436.3 kB
  • After minification 417.4 kB
  • After compression 67.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. Lazarusvintage.com needs all CSS files to be minified and compressed as it can save up to 368.6 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

69

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lazarusvintage.com

lazarusvintage.com

5841 ms

f6b4fdc4bc4d3ecd4943b5748a8e64d4.css

f6b4fdc4bc4d3ecd4943b5748a8e64d4.css

46 ms

225901f16acf2d38f7ccdbdbb9767067.css

225901f16acf2d38f7ccdbdbb9767067.css

151 ms

ea71c5be30307048eebfb763cfe55db5.css

ea71c5be30307048eebfb763cfe55db5.css

45 ms

prototype.js

prototype.js

126 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

103 ms

noconflict.js

noconflict.js

51 ms

ccard.js

ccard.js

57 ms

validation.js

validation.js

102 ms

builder.js

builder.js

77 ms

effects.js

effects.js

120 ms

dragdrop.js

dragdrop.js

99 ms

controls.js

controls.js

204 ms

slider.js

slider.js

130 ms

js.js

js.js

129 ms

form.js

form.js

201 ms

translate.js

translate.js

201 ms

cookies.js

cookies.js

206 ms

lightbox.js

lightbox.js

207 ms

jquery.min.js

jquery.min.js

210 ms

underscore.js

underscore.js

207 ms

backbone.js

backbone.js

206 ms

dropdown.js

dropdown.js

207 ms

calendar.js

calendar.js

224 ms

captcha.js

captcha.js

207 ms

calendar-setup.js

calendar-setup.js

219 ms

modernizr.custom.min.js

modernizr.custom.min.js

219 ms

selectivizr.js

selectivizr.js

219 ms

matchMedia.js

matchMedia.js

219 ms

matchMedia.addListener.js

matchMedia.addListener.js

218 ms

enquire.js

enquire.js

219 ms

app.js

app.js

231 ms

imagesloaded.js

imagesloaded.js

227 ms

minicart.js

minicart.js

226 ms

cmsmartmenu.js

cmsmartmenu.js

227 ms

thumbs.js

thumbs.js

227 ms

css

css

27 ms

css

css

39 ms

css

css

49 ms

f717d58d4e3cc96a3317b2cc51bd1d66.css

f717d58d4e3cc96a3317b2cc51bd1d66.css

288 ms

jquery-ui-1-10-4.js

jquery-ui-1-10-4.js

544 ms

ajaxlogin.js

ajaxlogin.js

201 ms

tm-stick-up.js

tm-stick-up.js

195 ms

owl.carousel.min.js

owl.carousel.min.js

198 ms

theme_old.js

theme_old.js

184 ms

bootstrap.js

bootstrap.js

187 ms

front.js

front.js

165 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

193 ms

jquery.fancybox.js

jquery.fancybox.js

183 ms

jquery.carouFredSel-6.2.1.js

jquery.carouFredSel-6.2.1.js

182 ms

cherry-fixed-parallax.js

cherry-fixed-parallax.js

181 ms

smoothing-scroll.js

smoothing-scroll.js

186 ms

ga.js

ga.js

11 ms

analytics.js

analytics.js

101 ms

new_lv_header.png

new_lv_header.png

102 ms

bdg_now_accepting_pp_2line_w.png

bdg_now_accepting_pp_2line_w.png

210 ms

img-1.jpg

img-1.jpg

91 ms

img-2.jpg

img-2.jpg

89 ms

img-4.jpg

img-4.jpg

91 ms

img-5.jpg

img-5.jpg

90 ms

nuagenowavaliable.jpg

nuagenowavaliable.jpg

91 ms

facebook.png

facebook.png

92 ms

twitter.png

twitter.png

92 ms

instagram.png

instagram.png

104 ms

__utm.gif

__utm.gif

51 ms

qwCYE106NwHxtQIaygqBug.ttf

qwCYE106NwHxtQIaygqBug.ttf

32 ms

IiMFELcoPB-OzGzq14k4eqCWcynf_cDxXwCLxiixG1c.ttf

IiMFELcoPB-OzGzq14k4eqCWcynf_cDxXwCLxiixG1c.ttf

52 ms

nBF2d6Y3AbOwfkBM-9HcWKCWcynf_cDxXwCLxiixG1c.ttf

nBF2d6Y3AbOwfkBM-9HcWKCWcynf_cDxXwCLxiixG1c.ttf

53 ms

4z2U46_RRLOfkoHsWJG3v6CWcynf_cDxXwCLxiixG1c.ttf

4z2U46_RRLOfkoHsWJG3v6CWcynf_cDxXwCLxiixG1c.ttf

51 ms

material-design.woff

material-design.woff

51 ms

collect

collect

182 ms

loader.gif

loader.gif

49 ms

collect

collect

159 ms

box-1.jpg

box-1.jpg

133 ms

sdk.js

sdk.js

9 ms

jk7b-Al_6RLn0YQzwF_1-fesZW2xOQ-xsNqO47m55DA.ttf

jk7b-Al_6RLn0YQzwF_1-fesZW2xOQ-xsNqO47m55DA.ttf

7 ms

widgets.js

widgets.js

109 ms

Accessibility Review

lazarusvintage.com accessibility score

100

Accessibility Issues

Best Practices

lazarusvintage.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

lazarusvintage.com SEO score

84

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

lazarusvintage.com

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