Tools & Wizards About Us
fbeyeequipments.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

fbeyeequipments.com

FBeye equipments | Home

Page Load Speed

1.7 sec in total

First Response

83 ms

Resources Loaded

1.1 sec

Page Rendered

518 ms

fbeyeequipments.com screenshot

About Website

Visit fbeyeequipments.com now to see the best up-to-date FBeye Equipments content and also check out these interesting facts you probably never knew about fbeyeequipments.com

Equipos oftalmológicos especializados, lo último en tecnologia para diagnóstico y cirugía, tratamiento del ojo seco, cataratas, glaucoma, retina, cornea. Los mejores equipos a tu alcance.

Visit fbeyeequipments.com

Key Findings

We analyzed Fbeyeequipments.com page load time and found that the first response time was 83 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

fbeyeequipments.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.364

29/100

15%

TTI (Time to Interactive)

Value9.7 s

28/100

10%

Network Requests Diagram

fbeyeequipments.com

83 ms

fbeyeequipments.com

406 ms

js

71 ms

bootstrap.min.css

114 ms

ionicons.css

140 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 85% of them (50 requests) were addressed to the original Fbeyeequipments.com, 12% (7 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (406 ms) belongs to the original domain Fbeyeequipments.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (45%)

Content Size

2.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fbeyeequipments.com main page is 2.5 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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 66.4 kB

  • Original 73.8 kB
  • After minification 58.6 kB
  • After compression 7.5 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 15.2 kB, which is 21% 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 66.4 kB or 90% of the original size.

Image Optimization

-11%

Potential reduce by 139.8 kB

  • Original 1.3 MB
  • After minification 1.1 MB

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, FBeye Equipments needs image optimization as it can save up to 139.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 422.7 kB

  • Original 598.4 kB
  • After minification 597.6 kB
  • After compression 175.7 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 422.7 kB or 71% of the original size.

CSS Optimization

-87%

Potential reduce by 497.3 kB

  • Original 570.4 kB
  • After minification 506.0 kB
  • After compression 73.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. Fbeyeequipments.com needs all CSS files to be minified and compressed as it can save up to 497.3 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (52%)

Requests Now

48

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fbeyeequipments.com

fbeyeequipments.com

83 ms

fbeyeequipments.com

fbeyeequipments.com

406 ms

js

js

71 ms

bootstrap.min.css

bootstrap.min.css

114 ms

ionicons.css

ionicons.css

140 ms

medwise-icons.css

medwise-icons.css

95 ms

vendors.min.css

vendors.min.css

98 ms

style.min.css

style.min.css

163 ms

components.min.css

components.min.css

135 ms

settings.css

settings.css

155 ms

layers.css

layers.css

224 ms

navigation.css

navigation.css

143 ms

mystyle.css

mystyle.css

170 ms

css2

css2

42 ms

logoFbeye.png

logoFbeye.png

348 ms

carrusel1.jpg

carrusel1.jpg

172 ms

carrusel2.jpg

carrusel2.jpg

213 ms

carrusel3.jpg

carrusel3.jpg

233 ms

carrusel4.jpg

carrusel4.jpg

236 ms

carrusel5.jpg

carrusel5.jpg

204 ms

carrusel6.jpg

carrusel6.jpg

212 ms

jquery.min.js

jquery.min.js

326 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

325 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

335 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

324 ms

revolution.extension.slideanims.min.js

revolution.extension.slideanims.min.js

325 ms

revolution.extension.migration.min.js

revolution.extension.migration.min.js

334 ms

revolution.extension.actions.min.js

revolution.extension.actions.min.js

334 ms

revolution.extension.layeranimation.min.js

revolution.extension.layeranimation.min.js

335 ms

revolution.extension.navigation.min.js

revolution.extension.navigation.min.js

336 ms

revolution.extension.parallax.min.js

revolution.extension.parallax.min.js

335 ms

jquery.appear.min.js

jquery.appear.min.js

335 ms

slick.min.js

slick.min.js

335 ms

jquery.countTo.min.js

jquery.countTo.min.js

336 ms

jquery-ui.min.js

jquery-ui.min.js

335 ms

script.min.js

script.min.js

337 ms

carrusel7.jpg

carrusel7.jpg

336 ms

aniversario.jpg

aniversario.jpg

361 ms

700-728-2.jpg

700-728-2.jpg

359 ms

logoFbeyeBco.png

logoFbeyeBco.png

359 ms

wa.png

wa.png

293 ms

cdmx.webp

cdmx.webp

290 ms

usa.webp

usa.webp

270 ms

brasil.webp

brasil.webp

269 ms

argentina.webp

argentina.webp

265 ms

peru.jpg

peru.jpg

261 ms

world-map-1.png

world-map-1.png

172 ms

world-map-2.png

world-map-2.png

173 ms

plecaMarcas.png

plecaMarcas.png

305 ms

ionicons.ttf

ionicons.ttf

171 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4jE-_F.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4jE-_F.ttf

38 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59E-_F.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59E-_F.ttf

166 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk79FO_F.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk79FO_F.ttf

189 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk6jFO_F.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk6jFO_F.ttf

190 ms

S6uyw4BMUTPHvxk.ttf

S6uyw4BMUTPHvxk.ttf

190 ms

S6u9w4BMUTPHh6UVew8.ttf

S6u9w4BMUTPHh6UVew8.ttf

190 ms

S6u9w4BMUTPHh50Xew8.ttf

S6u9w4BMUTPHh50Xew8.ttf

188 ms

loader.gif

loader.gif

52 ms

revicons.woff

revicons.woff

52 ms

Accessibility Review

fbeyeequipments.com accessibility score

58

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

Image elements do not have [alt] attributes

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

fbeyeequipments.com best practices score

83

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

Page has valid source maps

SEO Factors

fbeyeequipments.com SEO score

85

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

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

High

Document uses legible font sizes

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 Fbeyeequipments.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 Fbeyeequipments.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

fbeyeequipments.com

Open Graph description is not detected on the main page of FBeye Equipments. 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: