Tools & Wizards About Us
whyeyefight.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

whyeyefight.com

Age-Related Macular Degeneration Eye Vitamins from Bausch + Lomb

Page Load Speed

2.4 sec in total

First Response

161 ms

Resources Loaded

1.5 sec

Page Rendered

739 ms

whyeyefight.com screenshot

About Website

Click here to check amazing Why Eye Fight content for United States. Otherwise, check out these important facts you probably never knew about whyeyefight.com

PreserVision Eye Vitamins from Bausch + Lomb are designed for individuals diagnosed with moderate to advanced age-related macular degeneration (AMD).

Visit whyeyefight.com

Key Findings

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

Performance Metrics

whyeyefight.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value3,160 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

whyeyefight.com

161 ms

www.preservision.com

182 ms

jquery.js

37 ms

jquery-ui.js

60 ms

bundle.js

37 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Whyeyefight.com, 90% (46 requests) were made to Preservision.com and 2% (1 request) were made to Cdn.consentmanager.net. The less responsive or slowest element that took the longest time to load (651 ms) relates to the external source Cdn.consentmanager.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 596.2 kB (22%)

Content Size

2.7 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whyeyefight.com main page is 2.7 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 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 45.3 kB

  • Original 63.1 kB
  • After minification 59.9 kB
  • After compression 17.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 45.3 kB or 72% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.7 MB
  • After minification 1.7 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. Why Eye Fight images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 547.2 kB

  • Original 900.5 kB
  • After minification 900.5 kB
  • After compression 353.3 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 547.2 kB or 61% of the original size.

CSS Optimization

-9%

Potential reduce by 3.7 kB

  • Original 41.8 kB
  • After minification 41.8 kB
  • After compression 38.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. Whyeyefight.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (49%)

Requests Now

43

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whyeyefight.com

whyeyefight.com

161 ms

www.preservision.com

www.preservision.com

182 ms

jquery.js

jquery.js

37 ms

jquery-ui.js

jquery-ui.js

60 ms

bundle.js

bundle.js

37 ms

6008a5d051cc9.js

6008a5d051cc9.js

651 ms

bg-image.css

bg-image.css

28 ms

bootstrap.min.css

bootstrap.min.css

47 ms

main.min.css

main.min.css

49 ms

EPiServerForms.css

EPiServerForms.css

49 ms

find.js

find.js

49 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

94 ms

EPiServerForms.min.js

EPiServerForms.min.js

94 ms

jquery-ui.js

jquery-ui.js

97 ms

popper.min.js

popper.min.js

94 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

95 ms

E-v1.js

E-v1.js

22 ms

main.min.js

main.min.js

95 ms

gtm.js

gtm.js

127 ms

preservision_logo_header.svg

preservision_logo_header.svg

82 ms

img-531x700-homepage-banner.png

img-531x700-homepage-banner.png

89 ms

img-531x700-homepage-banner-mob.png

img-531x700-homepage-banner-mob.png

88 ms

eye2.png

eye2.png

85 ms

absorb2.png

absorb2.png

80 ms

pill2.png

pill2.png

86 ms

img-top-pres-store-curve.svg

img-top-pres-store-curve.svg

96 ms

preservision_store_logo.svg

preservision_store_logo.svg

89 ms

icon-pv-store1.svg

icon-pv-store1.svg

94 ms

icon-pv-store2.svg

icon-pv-store2.svg

122 ms

icon-pv-store3.svg

icon-pv-store3.svg

91 ms

preservision-box-coupon-1084x650-v1.png

preservision-box-coupon-1084x650-v1.png

124 ms

img-top-icon.png

img-top-icon.png

121 ms

img-areds-2-formula-CoQ10.png

img-areds-2-formula-CoQ10.png

126 ms

logoprimary-278x148.png

logoprimary-278x148.png

121 ms

icon-man-88x100.png

icon-man-88x100.png

119 ms

icon-q-105x105.png

icon-q-105x105.png

211 ms

save-60-icon.svg

save-60-icon.svg

211 ms

preservision_logo.png

preservision_logo.png

213 ms

icon-f-32x32.png

icon-f-32x32.png

214 ms

icon-insta-32x32.png

icon-insta-32x32.png

217 ms

icon-t-32x32.png

icon-t-32x32.png

215 ms

img-trust-arc-grey8.svg

img-trust-arc-grey8.svg

217 ms

ai.2.gbl.min.js

ai.2.gbl.min.js

197 ms

img-2400x1320wave-bg.png

img-2400x1320wave-bg.png

197 ms

GothamNarrow-Book.woff

GothamNarrow-Book.woff

201 ms

GothamNarrow-Bold.woff

GothamNarrow-Bold.woff

360 ms

Gotham-Bold.otf

Gotham-Bold.otf

128 ms

Gotham-Thin.otf

Gotham-Thin.otf

129 ms

Gotham-Medium.otf

Gotham-Medium.otf

130 ms

external-link-15X15.png

external-link-15X15.png

268 ms

GothamNarrow-Medium.woff

GothamNarrow-Medium.woff

162 ms

Accessibility Review

whyeyefight.com accessibility score

81

Accessibility Issues

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

whyeyefight.com SEO score

79

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whyeyefight.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 Whyeyefight.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

whyeyefight.com

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