6 sec in total
2.3 sec
3.6 sec
78 ms
Visit lensvector.com now to see the best up-to-date Lensvector content and also check out these interesting facts you probably never knew about lensvector.com
Visit lensvector.comWe analyzed Lensvector.com page load time and found that the first response time was 2.3 sec and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
lensvector.com performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value6.9 s
6/100
25%
Value6.9 s
33/100
10%
Value500 ms
58/100
30%
Value0.005
100/100
15%
Value7.3 s
49/100
10%
2336 ms
68 ms
153 ms
204 ms
216 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 91% of them (61 requests) were addressed to the original Lensvector.com, 4% (3 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Lensvector.com.
Page size can be reduced by 1.7 MB (79%)
2.2 MB
453.3 kB
In fact, the total size of Lensvector.com main page is 2.2 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. 65% of websites need less resources to load. CSS take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 39.8 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 39.8 kB or 77% of the original size.
Potential reduce by 1.4 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. Lensvector images are well optimized though.
Potential reduce by 610.9 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 610.9 kB or 72% of the original size.
Potential reduce by 1.1 MB
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. Lensvector.com needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 87% of the original size.
Number of requests can be reduced by 57 (90%)
63
6
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lensvector. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
lensvector.com
2336 ms
webfont.js
68 ms
wp-emoji-release.min.js
153 ms
pe2-display.css
204 ms
photoswipe.css
216 ms
dashicons.min.css
237 ms
jquery-ui-dialog.min.css
196 ms
layerslider.css
216 ms
styles.css
340 ms
bwg_frontend.css
337 ms
sumoselect.css
344 ms
font-awesome.css
357 ms
jquery.mCustomScrollbar.css
404 ms
settings.css
354 ms
style.css
534 ms
js_composer.min.css
735 ms
shortcodes.css
546 ms
responsive.css
429 ms
jetpack.css
470 ms
jquery.js
576 ms
jquery-migrate.min.js
544 ms
klass.min.js
552 ms
code.photoswipe.jquery-3.0.5.min.js
621 ms
layerslider.kreaturamedia.jquery.js
638 ms
jquery-easing-1.3.js
644 ms
jquerytransit.js
629 ms
layerslider.transitions.js
693 ms
bwg_frontend.js
702 ms
jquery.sumoselect.min.js
704 ms
jquery.mobile.js
830 ms
jquery.mCustomScrollbar.concat.min.js
713 ms
jquery.fullscreen-0.4.1.js
832 ms
bwg_gallery_box.js
834 ms
jquery.themepunch.tools.min.js
905 ms
jquery.themepunch.revolution.min.js
834 ms
css
29 ms
core.min.js
834 ms
devicepx-jetpack.js
6 ms
widget.min.js
833 ms
mouse.min.js
704 ms
resizable.min.js
660 ms
draggable.min.js
679 ms
button.min.js
672 ms
position.min.js
672 ms
dialog.min.js
720 ms
wpdialog.min.js
703 ms
editor.js
657 ms
jquery.form.min.js
648 ms
scripts.js
640 ms
jquery.easing.min.js
644 ms
waypoints.min.js
654 ms
waypoints-sticky.min.js
607 ms
prettyPhoto.js
622 ms
isotope.pkgd.min.js
581 ms
functions.js
580 ms
flexslider.min.js
516 ms
smoothscroll.js
525 ms
comment-reply.min.js
532 ms
wp-embed.min.js
560 ms
js_composer_front.js
527 ms
logo_white_LensVector.png
299 ms
logo_white_LensVector_retina.png
297 ms
spotlight_02.jpg
298 ms
Download_on_the_App_Store_Badge_US-UK_135x40.svg
299 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
9 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
13 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
11 ms
lensvector.com accessibility score
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
No form fields have multiple labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
lensvector.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
lensvector.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lensvector.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 Lensvector.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.
lensvector.com
Open Graph description is not detected on the main page of Lensvector. 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: