4.9 sec in total
680 ms
3 sec
1.3 sec
Visit seeclearly.com now to see the best up-to-date See Clearly content and also check out these interesting facts you probably never knew about seeclearly.com
See Clearly Vision offers expert eye care services to the greater Arlington, VA, area, including LASIK, cataract surgery, dry eye treatment and more.
Visit seeclearly.comWe analyzed Seeclearly.com page load time and found that the first response time was 680 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
seeclearly.com performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value4.2 s
43/100
25%
Value9.9 s
10/100
10%
Value2,160 ms
6/100
30%
Value0.291
41/100
15%
Value22.4 s
1/100
10%
680 ms
891 ms
73 ms
37 ms
116 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 24% of them (26 requests) were addressed to the original Seeclearly.com, 31% (33 requests) were made to Fonts.gstatic.com and 13% (14 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (891 ms) belongs to the original domain Seeclearly.com.
Page size can be reduced by 117.9 kB (11%)
1.1 MB
943.3 kB
In fact, the total size of Seeclearly.com main page is 1.1 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. 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 606.8 kB which makes up the majority of the site volume.
Potential reduce by 78.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. 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 78.7 kB or 80% of the original size.
Potential reduce by 19.6 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. See Clearly images are well optimized though.
Potential reduce by 1.6 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.
Potential reduce by 18.1 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. Seeclearly.com needs all CSS files to be minified and compressed as it can save up to 18.1 kB or 30% of the original size.
Number of requests can be reduced by 39 (70%)
56
17
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of See Clearly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
seeclearly.com
680 ms
www.seeclearly.com
891 ms
gtm.js
73 ms
fbevents.js
37 ms
1705419295-css3d46b6f4d77d4384600266c36aec36486c4eda04b5113715ba65ddbcf2cd8.css
116 ms
jquery-3.4.1.min.220afd743d.js
34 ms
5321905.js
204 ms
lazysizes.min.js
192 ms
webfont.js
74 ms
autoptimize_31d7926d5d72b3c721cd8bbfe7bb4059.js
271 ms
js
184 ms
analytics.js
180 ms
embed
363 ms
embed
558 ms
widget.js
299 ms
gtm.js
190 ms
css
232 ms
clearly-hero-1.jpg
301 ms
clearly-welcome-image-2.jpg
293 ms
clearly-cataract-homepage.jpg
230 ms
clearly-lasik-homepage.jpg
301 ms
clearly-crosslinking-homepage.jpg
429 ms
9BAAAAAQAAAAFtwAAAAAAAAAKABQAHgAyAEYAjACiAL4BFgE2AY4AAAABAAAADAA8AAMAAAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAADgCuAAEAAAAAAAEADQAAAAEAAAAAAAIABwCWAAEAAAAAAAMADQBIAAEAAAAAAAQADQCrAAEAAAAAAAUACwAnAAEAAAAAAAYADQBvAAEAAAAAAAoAGgDSAAMAAQQJAAEAGgANAAMAAQQJAAIADgCdAAMAAQQJAAMAGgBVAAMAAQQJAAQAGgC4AAMAAQQJAAUAFgAyAAMAAQQJAAYAGgB8AAMAAQQJAAoANADsd2ViZmxvdy1pY29ucwB3AGUAYgBmAGwAbwB3AC0AaQBjAG8AbgBzVmVyc2lvbiAxLjAAVgBlAHIAcwBpAG8AbgAgADEALgAwd2ViZmxvdy1pY29ucwB3AGUAYgBmAGwAbwB3AC0AaQBjAG8AbgBzd2ViZmxvdy1pY29ucwB3AGUAYgBmAGwAbwB3AC0AaQBjAG8AbgBzUmVndWxhcgBSAGUAZwB1AGwAYQByd2ViZmxvdy1pY29ucwB3AGUAYgBmAGwAbwB3AC0AaQBjAG8AbgBzRm9udCBnZW5lcmF0ZWQgYnkgSWNvTW9vbi4ARgBvAG4AdAAgAGcAZQBuAGUAcgBhAHQAZQBkACAAYgB5ACAASQBjAG8ATQBvAG8AbgAuAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
11 ms
collect
123 ms
see-clearly-logo.svg
116 ms
clearly-lasik-cta.jpg
251 ms
clearly-cataract-cta.jpg
121 ms
facebook_icon_white-f.svg
250 ms
youtube_white.png
251 ms
twitter-logo.svg
248 ms
instagram-icon-white.svg
250 ms
Linkedin-icon.png
305 ms
pixie.js
256 ms
233 ms
loader.js
209 ms
roundtrip.js
215 ms
js
224 ms
frontend.min.css
126 ms
action-bar.min.css
127 ms
popup.min.css
128 ms
hello.css
125 ms
inspire.css
125 ms
icegram.min.js
158 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUZiYCSUhiCnAw.ttf
136 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYCSUhiCnAw.ttf
265 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYCSUhiCnAw.ttf
316 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUZiYCSUhiCnAw.ttf
297 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYCSUhiCnAw.ttf
298 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYCSUhiCnAw.ttf
316 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJBbMl2xMBbKsUPpjl.ttf
494 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJN7Ml2xMBbKsUPpjl.ttf
314 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJabMl2xMBbKsUPpjl.ttf
493 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJt7Ml2xMBbKsUPpjl.ttf
493 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJ6bQl2xMBbKsUPpjl.ttf
343 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJ0LQl2xMBbKsUPpjl.ttf
453 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJt7Ql2xMBbKsUPpjl.ttf
454 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX9-p7K4GLs.ttf
398 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX9-p7K4GLs.ttf
400 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX9-p7K4GLs.ttf
400 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX9-p7K4GLs.ttf
401 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX9-p7K4GLs.ttf
403 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX9-p7K4GLs.ttf
404 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX9-p7K4GLs.ttf
404 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX9-p7K4GLs.ttf
406 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX9-p7K4GLs.ttf
407 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R8WXh0o5C8MLnrtQ.ttf
408 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR9WXh0o5C8MLnrtQ.ttf
409 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq_p9WXh0o5C8MLnrtQ.ttf
411 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXh0o5C8MLnrtQ.ttf
411 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9WXh0o5C8MLnrtQ.ttf
443 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq3p6WXh0o5C8MLnrtQ.ttf
444 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6WXh0o5C8MLnrtQ.ttf
444 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR6WXh0o5C8MLnrtQ.ttf
445 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqw16WXh0o5C8MLnrtQ.ttf
445 ms
SlGVmQWMvZQIdix7AFxXkHNSaBYXags.ttf
446 ms
SlGWmQWMvZQIdix7AFxXmMh3eDs1YiHKpWg.ttf
448 ms
widget_app_base_1705584376091.js
69 ms
call-tracking_7.js
21 ms
35 ms
bounce
179 ms
SCV-Dr-Mehta-Welcome-Social-Post-300x300.png
235 ms
sprite_1.png
127 ms
7H5QV4E3ZVHZTEHCGHMAOK
102 ms
wcm
28 ms
GPJX22LGRZE3HNZSOL3JOH.js
41 ms
wcm
39 ms
out
20 ms
out
55 ms
out
65 ms
out
64 ms
out
64 ms
out
65 ms
out
65 ms
out
66 ms
out
67 ms
out
66 ms
out
67 ms
out
69 ms
sync
151 ms
pixel
126 ms
tap.php
109 ms
Pug
106 ms
setuid
115 ms
xuid
5 ms
in
3 ms
sd
37 ms
rum
26 ms
seeclearly.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
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
seeclearly.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
seeclearly.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
Image elements do not have [alt] attributes
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 Seeclearly.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 Seeclearly.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.
seeclearly.com
Open Graph data is detected on the main page of See Clearly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: