Tools & Wizards About Us
lenzworks.com screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

lenzworks.com

Lenzworks | Through our Lenz, it just works!

Page Load Speed

1.6 sec in total

First Response

121 ms

Resources Loaded

577 ms

Page Rendered

945 ms

lenzworks.com screenshot

About Website

Welcome to lenzworks.com homepage info - get ready to check Lenzworks best content right away, or after learning these important things about lenzworks.com

Visit lenzworks.com

Key Findings

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

Performance Metrics

lenzworks.com performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value17.4 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

lenzworks.com

121 ms

modules-style.css

23 ms

magnific-popup.min.css

30 ms

frontend.css

27 ms

slick.min.css

31 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 80% of them (64 requests) were addressed to the original Lenzworks.com, 19% (15 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (256 ms) belongs to the original domain Lenzworks.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 174.6 kB (4%)

Content Size

4.7 MB

After Optimization

4.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lenzworks.com main page is 4.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.3 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 124.8 kB

  • Original 148.3 kB
  • After minification 144.8 kB
  • After compression 23.5 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 124.8 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 45.0 kB

  • Original 4.3 MB
  • After minification 4.2 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. Lenzworks images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 3.3 kB

  • Original 215.1 kB
  • After minification 215.1 kB
  • After compression 211.8 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

-2%

Potential reduce by 1.5 kB

  • Original 86.4 kB
  • After minification 86.2 kB
  • After compression 84.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. Lenzworks.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

63

After Optimization

32

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lenzworks.com

lenzworks.com

121 ms

modules-style.css

modules-style.css

23 ms

magnific-popup.min.css

magnific-popup.min.css

30 ms

frontend.css

frontend.css

27 ms

slick.min.css

slick.min.css

31 ms

magnific-popup.min.css

magnific-popup.min.css

36 ms

frontend.css

frontend.css

39 ms

style.min.css

style.min.css

48 ms

css

css

35 ms

magnific_popup.css

magnific_popup.css

42 ms

swiper.css

swiper.css

46 ms

popup.css

popup.css

44 ms

animate.css

animate.css

61 ms

readmore.css

readmore.css

62 ms

style.css

style.css

63 ms

jquery.min.js

jquery.min.js

69 ms

jquery-migrate.min.js

jquery-migrate.min.js

67 ms

magnific-popup.js

magnific-popup.js

67 ms

slick.min.js

slick.min.js

80 ms

counter-up.min.js

counter-up.min.js

67 ms

frontend.js

frontend.js

82 ms

slick.min.js

slick.min.js

82 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

89 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

83 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

98 ms

wp-polyfill.min.js

wp-polyfill.min.js

86 ms

react.min.js

react.min.js

93 ms

react-dom.min.js

react-dom.min.js

100 ms

frontend.js

frontend.js

94 ms

scripts.min.js

scripts.min.js

110 ms

jquery.fitvids.js

jquery.fitvids.js

106 ms

common.js

common.js

107 ms

lenzworks_logo_notag.png

lenzworks_logo_notag.png

210 ms

welcome_header_2.png

welcome_header_2.png

209 ms

lz_stats_2.png

lz_stats_2.png

206 ms

our_clients_hdr.png

our_clients_hdr.png

209 ms

client_logo_aeris-1.png

client_logo_aeris-1.png

207 ms

client_logo_arches-1.png

client_logo_arches-1.png

209 ms

client_logo_byu_tv-1.png

client_logo_byu_tv-1.png

196 ms

client_logo_disney_vc-1.png

client_logo_disney_vc-1.png

194 ms

client_logo_exploria-1.png

client_logo_exploria-1.png

193 ms

client_logo_mitsubishi-1.png

client_logo_mitsubishi-1.png

191 ms

client_logo_nat_geo_wild-1.png

client_logo_nat_geo_wild-1.png

186 ms

client_logo_palladium-1.png

client_logo_palladium-1.png

192 ms

client_logo_rci-1.png

client_logo_rci-1.png

185 ms

client_logo_rr-1.png

client_logo_rr-1.png

203 ms

client_logo_rukus-1.png

client_logo_rukus-1.png

187 ms

client_logo_snowbird-1.png

client_logo_snowbird-1.png

185 ms

client_logo_uofu-1.png

client_logo_uofu-1.png

190 ms

client_logo_welk-1.png

client_logo_welk-1.png

198 ms

client_logo_wyndham-1.png

client_logo_wyndham-1.png

210 ms

client_wall.png

client_wall.png

211 ms

our_work_hdr.png

our_work_hdr.png

218 ms

lz_vidpi_RR2.png

lz_vidpi_RR2.png

237 ms

lz_vidpi_Hometeam.png

lz_vidpi_Hometeam.png

207 ms

lz_vidpi_RR.png

lz_vidpi_RR.png

240 ms

lz_vidpi_LZ.png

lz_vidpi_LZ.png

224 ms

lz_vidpi_USOA.png

lz_vidpi_USOA.png

228 ms

lz_vidpi_Defunkify.png

lz_vidpi_Defunkify.png

256 ms

lz_vidpi_DiningDean.png

lz_vidpi_DiningDean.png

254 ms

lz_vidpi_Casting.png

lz_vidpi_Casting.png

256 ms

header_lutys.png

header_lutys.png

256 ms

pxiByp8kv8JHgFVrLGT9V1s.ttf

pxiByp8kv8JHgFVrLGT9V1s.ttf

28 ms

pxiEyp8kv8JHgFVrFJA.ttf

pxiEyp8kv8JHgFVrFJA.ttf

33 ms

pxiByp8kv8JHgFVrLDz8V1s.ttf

pxiByp8kv8JHgFVrLDz8V1s.ttf

43 ms

pxiByp8kv8JHgFVrLFj_V1s.ttf

pxiByp8kv8JHgFVrLFj_V1s.ttf

46 ms

pxiGyp8kv8JHgFVrLPTedw.ttf

pxiGyp8kv8JHgFVrLPTedw.ttf

46 ms

pxiByp8kv8JHgFVrLEj6V1s.ttf

pxiByp8kv8JHgFVrLEj6V1s.ttf

47 ms

pxiByp8kv8JHgFVrLCz7V1s.ttf

pxiByp8kv8JHgFVrLCz7V1s.ttf

55 ms

pxiByp8kv8JHgFVrLDD4V1s.ttf

pxiByp8kv8JHgFVrLDD4V1s.ttf

56 ms

pxiByp8kv8JHgFVrLBT5V1s.ttf

pxiByp8kv8JHgFVrLBT5V1s.ttf

56 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvgUE.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvgUE.ttf

58 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvgUE.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvgUE.ttf

56 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs169vgUE.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs169vgUE.ttf

56 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs13FvgUE.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs13FvgUE.ttf

57 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9ogUE.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9ogUE.ttf

58 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZogUE.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZogUE.ttf

58 ms

modules.woff

modules.woff

125 ms

style.min.css

style.min.css

20 ms

style.min.css

style.min.css

16 ms

Accessibility Review

lenzworks.com accessibility score

70

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

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

SEO Factors

lenzworks.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

lenzworks.com

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