3.4 sec in total
283 ms
2.9 sec
210 ms
Welcome to welovelenses.com homepage info - get ready to check Welovelenses best content for United Kingdom right away, or after learning these important things about welovelenses.com
| Contact lenses online. Contact lenses of leading brands. Contact lenses at low prices from %sitenamepage%%
Visit welovelenses.comWe analyzed Welovelenses.com page load time and found that the first response time was 283 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
welovelenses.com performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value14.4 s
0/100
25%
Value8.9 s
15/100
10%
Value1,440 ms
15/100
30%
Value0.132
81/100
15%
Value14.1 s
9/100
10%
283 ms
512 ms
49 ms
55 ms
47 ms
Our browser made a total of 139 requests to load all elements on the main page. We found that 83% of them (116 requests) were addressed to the original Welovelenses.com, 9% (12 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Welovelenses.com.
Page size can be reduced by 275.9 kB (30%)
922.4 kB
646.5 kB
In fact, the total size of Welovelenses.com main page is 922.4 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. 75% 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 576.9 kB which makes up the majority of the site volume.
Potential reduce by 268.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 268.8 kB or 85% of the original size.
Potential reduce by 7.0 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. Welovelenses images are well optimized though.
Potential reduce by 111 B
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.
Number of requests can be reduced by 101 (83%)
121
20
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Welovelenses. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 64 to 1 for JavaScripts and from 39 to 1 for CSS and as a result speed up the page load time.
welovelenses.com
283 ms
www.welovelenses.com
512 ms
formidableforms.css
49 ms
style-index.css
55 ms
frontend.min.css
47 ms
frontend.css
43 ms
premium-addons.min.css
75 ms
followups.css
92 ms
woocommerce-layout.css
93 ms
style.min.css
92 ms
pagenavi-css.css
89 ms
header-footer-elementor.css
126 ms
elementor-icons.min.css
119 ms
frontend-lite.min.css
121 ms
swiper.min.css
103 ms
post-56559.css
138 ms
frontend-lite.min.css
126 ms
global.css
143 ms
post-62085.css
152 ms
style.css
148 ms
select2.min.css
154 ms
slick.css
155 ms
slick-theme.css
168 ms
slabtext.css
172 ms
tipped.css
183 ms
remodal.css
203 ms
remodal-default-theme.css
177 ms
wll.css
184 ms
style.basic.css
203 ms
style-curvy-blue.css
205 ms
free-shipping.css
212 ms
shiftnav.min.css
210 ms
font-awesome.min.css
273 ms
css
48 ms
fontawesome.min.css
249 ms
solid.min.css
236 ms
smartslider.min.css
231 ms
jquery.min.js
240 ms
js
82 ms
js
110 ms
css
56 ms
jquery-migrate.min.js
208 ms
script.min.js
232 ms
fue-account-subscriptions.js
254 ms
jquery.blockUI.min.js
254 ms
add-to-cart.min.js
217 ms
js.cookie.min.js
307 ms
woocommerce.min.js
306 ms
captaincore-analytics.js
392 ms
n2.min.js
410 ms
tp.widget.sync.bootstrap.min.js
33 ms
16970.js
405 ms
wc-blocks.css
385 ms
slick.min.css
379 ms
smartslider-frontend.min.js
366 ms
ss-simple.min.js
362 ms
w-arrow-image.min.js
379 ms
dismissible-wp-notices.js
376 ms
ajax-geolocation.min.js
365 ms
fue-front.js
355 ms
sourcebuster.min.js
352 ms
order-attribution.min.js
443 ms
frontend-checkout.min.js
439 ms
skip-link-focus-fix.js
440 ms
select2.min.js
428 ms
slick.min.js
421 ms
modernizr-custom.js
415 ms
jquery.slabtext.min.js
548 ms
tipped.js
544 ms
masonry.pkgd.min.js
527 ms
remodal.min.js
540 ms
jquery.sticky-kit.min.js
525 ms
js.cookie-2.1.4.min.js
518 ms
wll.js
535 ms
underscore.min.js
575 ms
asl-prereq.js
575 ms
asl-core.js
571 ms
asl-results-vertical.js
501 ms
asl-autocomplete.js
554 ms
asl-load.js
542 ms
asl-wrapper.js
515 ms
smush-lazy-load-native.min.js
513 ms
gtm.js
178 ms
analytics.js
187 ms
shiftnav.min.js
424 ms
isotope.min.js
424 ms
jquery.flexslider.min.js
423 ms
slick.min.js
367 ms
imagesloaded.min.js
338 ms
premium-woo-products.min.js
337 ms
webpack-pro.runtime.min.js
339 ms
webpack.runtime.min.js
336 ms
frontend-modules.min.js
361 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
162 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVQ.woff
162 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff
235 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff
235 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff
197 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff
194 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
234 ms
KFOmCnqEu92Fr1Mu4mxM.woff
196 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
237 ms
KFOkCnqEu92Fr1MmgVxIIzQ.woff
251 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
250 ms
KFOlCnqEu92Fr1MmYUtfBBc-.woff
251 ms
wp-polyfill-inert.min.js
351 ms
regenerator-runtime.min.js
353 ms
wp-polyfill.min.js
352 ms
hooks.min.js
351 ms
i18n.min.js
355 ms
frontend.min.js
356 ms
xfbml.customerchat.js
234 ms
waypoints.min.js
266 ms
core.min.js
270 ms
frontend.min.js
268 ms
elements-handlers.min.js
274 ms
welovelenses.woff
385 ms
fa-solid-900.woff
349 ms
www.welovelenses.com
1329 ms
pretot-banner-1900x315-min.jpg
263 ms
Prec1-banner-1900x315-min.jpg
391 ms
tp.widget.bootstrap.min.js
74 ms
WLL-banner-1900x315-min.jpg
379 ms
blg-banner-1900x315-min.jpg
380 ms
PreTot-banner-600x315-min.jpg
372 ms
Prec1-banner-600x315-min.jpg
375 ms
WLL-banner-600x315-min.jpg
313 ms
blg-banner-600x315-min.jpg
404 ms
bcg2.png
311 ms
logo-welovelenses.png
280 ms
logo-lens-2-see-header.jpg
280 ms
327 ms
dacp30-min-300x225.jpg
51 ms
soflens-daily-disposable-30-lenses-300x225.jpg
50 ms
dacp90-min-300x225.jpg
49 ms
total1-min-300x225.jpg
48 ms
Acuvue-Oasys-1-Day-30-contact-lenses-300x225.webp
49 ms
Precision1-min-300x225.jpg
82 ms
woocommerce-smallscreen.css
64 ms
welovelenses.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Some elements have a [tabindex] value greater than 0
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
welovelenses.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
welovelenses.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Welovelenses.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 Welovelenses.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.
welovelenses.com
Open Graph description is not detected on the main page of Welovelenses. 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: