2.8 sec in total
364 ms
2 sec
471 ms
Visit seevividly.com now to see the best up-to-date See Vivid Ly content for United States and also check out these interesting facts you probably never knew about seevividly.com
At-home and in-clinic vision training. For amblyopia, strabismus, and convergence insufficiency. Find the best eye doctor near you to prescribe VR eye exercises.
Visit seevividly.comWe analyzed Seevividly.com page load time and found that the first response time was 364 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
seevividly.com performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value39.0 s
0/100
25%
Value28.9 s
0/100
10%
Value3,270 ms
2/100
30%
Value0.743
6/100
15%
Value42.8 s
0/100
10%
364 ms
25 ms
22 ms
38 ms
92 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 62% of them (66 requests) were addressed to the original Seevividly.com, 17% (18 requests) were made to Fonts.gstatic.com and 6% (6 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (697 ms) relates to the external source Youtube.com.
Page size can be reduced by 677.7 kB (14%)
4.8 MB
4.1 MB
In fact, the total size of Seevividly.com main page is 4.8 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. Only a small number of websites need less resources to load. Images take 3.9 MB which makes up the majority of the site volume.
Potential reduce by 54.0 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 10.6 kB, which is 16% 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 54.0 kB or 80% of the original size.
Potential reduce by 582.9 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. Obviously, See Vivid Ly needs image optimization as it can save up to 582.9 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 14.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 26.2 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. Seevividly.com has all CSS files already compressed.
Number of requests can be reduced by 36 (53%)
68
32
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of See Vivid Ly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
www.seevividly.com
364 ms
jquery.min.js
25 ms
jquery.localize.min.js
22 ms
jquery.3.1.0.min.js
38 ms
css
92 ms
bootstrap.min.css
38 ms
all.css
24 ms
all.min.css
71 ms
bootstrap.min.js
70 ms
recaptcha_ajax.js
84 ms
css
146 ms
sawarabigothic.css
202 ms
bootstrap.min.css
76 ms
essentials.css
79 ms
layout.css
79 ms
header-1.css
70 ms
orange.css
82 ms
adsbygoogle.js
149 ms
template.css
82 ms
jquery-2.2.3.min.js
85 ms
scripts.js
86 ms
jquery.cookie.js
82 ms
layerslider_pack.js
143 ms
demo.layerslider_slider.js
81 ms
layerslider.css
83 ms
js
146 ms
fbevents.js
341 ms
us.png
318 ms
5Sr42ZdInfE
622 ms
MyXuoVzs2Uc
697 ms
HIPAA-Website-Verified-Seal.png
481 ms
de.png
76 ms
jp.png
76 ms
cn.png
76 ms
logo_header_us.png
76 ms
Dr_Shumaker.jpeg
77 ms
slide-b-1.png
217 ms
slide-b-2.png
196 ms
slide-b-3.png
192 ms
slide-b-4.png
192 ms
slide-b-5.png
192 ms
dpvr_p1_pro_box.png
191 ms
vivid_vision_patient_success_stories.png
345 ms
vvp-landing-dark.jpg
202 ms
18-min.jpg
204 ms
infoGFX_stage1.png
201 ms
infoGFX_stage2.png
203 ms
infoGFX_stage3.png
214 ms
infoGFX_stage4.png
214 ms
infoGFX_stage5.png
215 ms
productshot_icon_clinic.png
233 ms
dpvr_p1_pro_productshot_icon_home.png
236 ms
world-map.png
233 ms
footer_sprite.png
235 ms
ce_mark.png
234 ms
ec_rep.jpg
238 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
146 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
165 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
183 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
183 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
195 ms
font-icons.woff
195 ms
fontawesome-webfont.woff
194 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf
193 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexQ.ttf
192 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf
305 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf
197 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf
196 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf
199 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf
199 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf
289 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf
299 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf
288 ms
glyphicons-halflings-regular.woff
190 ms
glyphicons-halflings-regular.woff
196 ms
fa-solid-900.woff
194 ms
fa-solid-900.woff
285 ms
fa-regular-400.woff
194 ms
fa-regular-400.woff
288 ms
S6u9w4BMUTPHh7USSwiPHA.ttf
304 ms
S6uyw4BMUTPHjx4wWw.ttf
303 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
304 ms
analytics.js
133 ms
plusone.js
127 ms
landing-c.json
232 ms
global-c.json
234 ms
bootstrap.min.js
231 ms
smoothscroll.js
230 ms
skin.css
211 ms
cb=gapi.loaded_0
94 ms
linkid.js
89 ms
www-player.css
81 ms
www-embed-player.js
133 ms
base.js
261 ms
glyphicons-halflings-regular.ttf
119 ms
collect
99 ms
collect
390 ms
fa-solid-900.ttf
50 ms
fa-regular-400.ttf
51 ms
vvp-landing-dark.jpg
315 ms
ad_status.js
301 ms
glyphicons-halflings-regular.svg
250 ms
fa-solid-900.svg
249 ms
fa-regular-400.svg
250 ms
UCY5Klx_0fJhMytIltuKLUwnjJON9GWedkq6jjIrpW0.js
196 ms
embed.js
147 ms
seevividly.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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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.
seevividly.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
Browser errors were logged to the console
Page has valid source maps
seevividly.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Seevividly.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 Seevividly.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.
seevividly.com
Open Graph data is detected on the main page of See Vivid Ly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: