Tools & Wizards About Us
futurovision.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

futurovision.com

Inicio - Futuro vision

Page Load Speed

3.7 sec in total

First Response

277 ms

Resources Loaded

3.2 sec

Page Rendered

303 ms

futurovision.com screenshot

About Website

Click here to check amazing Futuro Vision content for Peru. Otherwise, check out these important facts you probably never knew about futurovision.com

Somos una Clínica Especializada en Cirugía Refractiva Láser, Catarata, Carnosidad, Glaucoma. Prev

Visit futurovision.com

Key Findings

We analyzed Futurovision.com page load time and found that the first response time was 277 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

futurovision.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value4,060 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value17.3 s

4/100

10%

Network Requests Diagram

www.futurovision.com

277 ms

css

33 ms

theme.min.css

60 ms

style.css

64 ms

frontend.css

68 ms

Our browser made a total of 155 requests to load all elements on the main page. We found that 86% of them (133 requests) were addressed to the original Futurovision.com, 6% (9 requests) were made to Fonts.gstatic.com and 3% (4 requests) were made to Lw.cliengo.com. The less responsive or slowest element that took the longest time to load (280 ms) belongs to the original domain Futurovision.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 331.7 kB (42%)

Content Size

789.7 kB

After Optimization

458.0 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Futurovision.com main page is 789.7 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. 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 409.6 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 331.4 kB

  • Original 379.5 kB
  • After minification 371.4 kB
  • After compression 48.1 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 331.4 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 171 B

  • Original 409.6 kB
  • After minification 409.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. Futuro Vision images are well optimized though.

CSS Optimization

-19%

Potential reduce by 116 B

  • Original 610 B
  • After minification 610 B
  • After compression 494 B

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. Futurovision.com needs all CSS files to be minified and compressed as it can save up to 116 B or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 109 (76%)

Requests Now

144

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.futurovision.com

www.futurovision.com

277 ms

css

css

33 ms

theme.min.css

theme.min.css

60 ms

style.css

style.css

64 ms

frontend.css

frontend.css

68 ms

style.css

style.css

65 ms

styles.css

styles.css

70 ms

wpcf7-redirect-frontend.min.css

wpcf7-redirect-frontend.min.css

70 ms

style.min.css

style.min.css

78 ms

header-footer.min.css

header-footer.min.css

85 ms

custom-frontend-lite.min.css

custom-frontend-lite.min.css

88 ms

post-1262.css

post-1262.css

87 ms

all.min.css

all.min.css

92 ms

v4-shims.min.css

v4-shims.min.css

95 ms

public.css

public.css

98 ms

jet-popup-frontend.css

jet-popup-frontend.css

107 ms

custom-jet-blocks.css

custom-jet-blocks.css

107 ms

jet-elements.css

jet-elements.css

110 ms

jet-elements-skin.css

jet-elements-skin.css

118 ms

swiper.min.css

swiper.min.css

120 ms

custom-pro-frontend-lite.min.css

custom-pro-frontend-lite.min.css

120 ms

main.css

main.css

128 ms

jet-blog.css

jet-blog.css

129 ms

jet-tabs-frontend.css

jet-tabs-frontend.css

134 ms

global.css

global.css

136 ms

post-8.css

post-8.css

138 ms

post-1392.css

post-1392.css

137 ms

post-1817.css

post-1817.css

150 ms

post-2534.css

post-2534.css

149 ms

post-3231.css

post-3231.css

152 ms

post-1270.css

post-1270.css

156 ms

post-1302.css

post-1302.css

154 ms

ekiticons.css

ekiticons.css

160 ms

style.css

style.css

170 ms

flatpickr.min.css

flatpickr.min.css

20 ms

chosen.min.css

chosen.min.css

179 ms

jet-search.css

jet-search.css

180 ms

widget-styles.css

widget-styles.css

221 ms

js

js

73 ms

js

js

131 ms

flatpickr

flatpickr

3 ms

responsive.css

responsive.css

144 ms

general.min.css

general.min.css

130 ms

modern.css

modern.css

135 ms

1394.css

1394.css

140 ms

custom-widget-icon-list.min.css

custom-widget-icon-list.min.css

138 ms

custom-pro-widget-nav-menu.min.css

custom-pro-widget-nav-menu.min.css

136 ms

post-3239.css

post-3239.css

142 ms

post-2892.css

post-2892.css

140 ms

post-2888.css

post-2888.css

168 ms

animations.min.css

animations.min.css

166 ms

jquery.min.js

jquery.min.js

162 ms

jquery-migrate.min.js

jquery-migrate.min.js

166 ms

imagesloaded.min.js

imagesloaded.min.js

169 ms

main.min.js

main.min.js

169 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

243 ms

underscore.min.js

underscore.min.js

156 ms

wp-util.min.js

wp-util.min.js

148 ms

chosen.jquery.min.js

chosen.jquery.min.js

147 ms

jet-plugins.js

jet-plugins.js

146 ms

jet-search.js

jet-search.js

229 ms

index.js

index.js

222 ms

index.js

index.js

218 ms

wpcf7r-fe.js

wpcf7r-fe.js

217 ms

njt-whatsapp.js

njt-whatsapp.js

215 ms

whatsapp-button.js

whatsapp-button.js

225 ms

hello-frontend.min.js

hello-frontend.min.js

217 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

219 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

216 ms

wp-polyfill.min.js

wp-polyfill.min.js

211 ms

hooks.min.js

hooks.min.js

213 ms

vue.min.js

vue.min.js

205 ms

jet-menu-public-scripts.js

jet-menu-public-scripts.js

201 ms

anime.min.js

anime.min.js

194 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

190 ms

jet-popup-frontend.js

jet-popup-frontend.js

191 ms

ooohboi-steroids.js

ooohboi-steroids.js

191 ms

frontend-script.js

frontend-script.js

182 ms

widget-scripts.js

widget-scripts.js

280 ms

general.min.js

general.min.js

276 ms

slick.min.js

slick.min.js

276 ms

frontend.js

frontend.js

272 ms

jquery-numerator.min.js

jquery-numerator.min.js

265 ms

imagesloaded.min.js

imagesloaded.min.js

234 ms

macy.js

macy.js

233 ms

whatsapp-popup.js

whatsapp-popup.js

223 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

221 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

220 ms

webpack.runtime.min.js

webpack.runtime.min.js

221 ms

frontend-modules.min.js

frontend-modules.min.js

220 ms

i18n.min.js

i18n.min.js

219 ms

frontend.min.js

frontend.min.js

220 ms

gtm.js

gtm.js

94 ms

waypoints.min.js

waypoints.min.js

198 ms

core.min.js

core.min.js

139 ms

frontend.min.js

frontend.min.js

139 ms

elements-handlers.min.js

elements-handlers.min.js

137 ms

jet-blocks.min.js

jet-blocks.min.js

137 ms

jet-elements.min.js

jet-elements.min.js

136 ms

widgets-scripts.js

widgets-scripts.js

136 ms

jet-popup-elementor-frontend.js

jet-popup-elementor-frontend.js

135 ms

jet-tabs-frontend.min.js

jet-tabs-frontend.min.js

123 ms

animate-circle.min.js

animate-circle.min.js

122 ms

elementor.js

elementor.js

122 ms

jquery.sticky.min.js

jquery.sticky.min.js

121 ms

jet-blog.min.js

jet-blog.min.js

120 ms

lazyload.min.js

lazyload.min.js

120 ms

LOGO-FV-2023-NUEVO-COLOR-1_Letterhead-copia.svg

LOGO-FV-2023-NUEVO-COLOR-1_Letterhead-copia.svg

119 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4lM3OwRmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4lM3OwRmPg.ttf

69 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4mE3OwRmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4mE3OwRmPg.ttf

219 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4g03OwRmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4g03OwRmPg.ttf

220 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4tM3OwRmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4tM3OwRmPg.ttf

266 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4lM2OwRmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4lM2OwRmPg.ttf

264 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4o0wOwRmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4o0wOwRmPg.ttf

265 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4rQwOwRmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4rQwOwRmPg.ttf

263 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4tMwOwRmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4tMwOwRmPg.ttf

264 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4vowOwRmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4vowOwRmPg.ttf

261 ms

elementskit.woff

elementskit.woff

255 ms

www.futurovision.com

www.futurovision.com

93 ms

66158106a8a91200327fde71.js

66158106a8a91200327fde71.js

108 ms

WhatsApp-Image-2023-10-18-at-11.05.11-AM-1024x768.jpeg

WhatsApp-Image-2023-10-18-at-11.05.11-AM-1024x768.jpeg

40 ms

Patron-6.svg

Patron-6.svg

32 ms

Patron-3.svg

Patron-3.svg

29 ms

img-1_11zon.webp

img-1_11zon.webp

34 ms

124.jpg

124.jpg

30 ms

img-2.jpg

img-2.jpg

30 ms

PROCEDIMIENTOS-ESPECIALES-EXTERNO-E-INTERNO-1024x683.webp

PROCEDIMIENTOS-ESPECIALES-EXTERNO-E-INTERNO-1024x683.webp

49 ms

Consulta-integral.svg

Consulta-integral.svg

52 ms

OPTICA-final-1024x683.webp

OPTICA-final-1024x683.webp

54 ms

FARMACIA-EXTERNA-E-INTERNA.webp

FARMACIA-EXTERNA-E-INTERNA.webp

55 ms

img-3.webp

img-3.webp

54 ms

EXAMENES-AUXILIARES-INTERNO-1024x682.webp

EXAMENES-AUXILIARES-INTERNO-1024x682.webp

80 ms

DSC02093-1-1024x576.webp

DSC02093-1-1024x576.webp

70 ms

patron1.svg

patron1.svg

76 ms

image-16-min.png

image-16-min.png

79 ms

la-positiva-2.png

la-positiva-2.png

79 ms

mapfre.png

mapfre.png

80 ms

pacifico-eps-2-1.png

pacifico-eps-2-1.png

90 ms

Logo-9-min.png

Logo-9-min.png

136 ms

Logo-9-1-min.png

Logo-9-1-min.png

136 ms

Logo-9-2-min.png

Logo-9-2-min.png

135 ms

Logo-9-3-min.png

Logo-9-3-min.png

134 ms

la-protectora-1.png

la-protectora-1.png

137 ms

petroperu-1.png

petroperu-1.png

136 ms

Patron-3-1.svg

Patron-3-1.svg

137 ms

lentes-de-contacto-a-medida-scaled.jpg

lentes-de-contacto-a-medida-scaled.jpg

160 ms

lesiones-oculares-1024x626.jpg

lesiones-oculares-1024x626.jpg

139 ms

futuro-vision-blog-salud-visual-1024x512.jpg

futuro-vision-blog-salud-visual-1024x512.jpg

145 ms

creditos-staff-1.svg

creditos-staff-1.svg

139 ms

mainclgo.bundle.js

mainclgo.bundle.js

31 ms

66158106a8a91200327fde71

66158106a8a91200327fde71

33 ms

widget.css

widget.css

21 ms

style.css

style.css

107 ms

widget.js

widget.js

30 ms

App.css

App.css

3 ms

Accessibility Review

futurovision.com accessibility score

84

Accessibility Issues

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

Buttons do not have an accessible name

High

Form elements do not have associated labels

High

Links do not have a discernible name

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.

Best Practices

futurovision.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

futurovision.com SEO score

91

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Futurovision.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Futurovision.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

futurovision.com

Open Graph data is detected on the main page of Futuro Vision. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: