Tools & Wizards About Us
fodo.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

fodo.com

FODO - The Association for Eye Care Providers | Home

Page Load Speed

3.9 sec in total

First Response

33 ms

Resources Loaded

3.7 sec

Page Rendered

198 ms

fodo.com screenshot

About Website

Welcome to fodo.com homepage info - get ready to check FODO best content right away, or after learning these important things about fodo.com

The Association for UK eye care providers. Become a member and benefit from Medical malpractice insurance, Legal defence, Guidance and more. Be heard and shape the future of eye care.

Visit fodo.com

Key Findings

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

Performance Metrics

fodo.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value550 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0.724

6/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

fodo.com

33 ms

fodo.com

364 ms

www.fodo.com

1636 ms

css

49 ms

css

48 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 84% of them (46 requests) were addressed to the original Fodo.com, 5% (3 requests) were made to Fonts.googleapis.com and 4% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Fodo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 205.9 kB (12%)

Content Size

1.8 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-87%

Potential reduce by 43.0 kB

  • Original 49.2 kB
  • After minification 24.8 kB
  • After compression 6.2 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 24.4 kB, which is 50% 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 43.0 kB or 87% of the original size.

Image Optimization

-10%

Potential reduce by 158.5 kB

  • Original 1.6 MB
  • After minification 1.4 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. FODO images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 479 B

  • Original 110.9 kB
  • After minification 110.9 kB
  • After compression 110.4 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.

CSS Optimization

-6%

Potential reduce by 3.9 kB

  • Original 63.8 kB
  • After minification 63.8 kB
  • After compression 59.9 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. Fodo.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (61%)

Requests Now

49

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fodo.com

fodo.com

33 ms

fodo.com

fodo.com

364 ms

www.fodo.com

www.fodo.com

1636 ms

css

css

49 ms

css

css

48 ms

jqueryui.css

jqueryui.css

120 ms

nav.css

nav.css

150 ms

sitev5.css

sitev5.css

134 ms

plattermenuv5.css

plattermenuv5.css

144 ms

standardv5.css

standardv5.css

147 ms

overlay-apple2.css

overlay-apple2.css

132 ms

tabs-panes.css

tabs-panes.css

234 ms

jquery.lightbox-0.5.css

jquery.lightbox-0.5.css

233 ms

scrollable-buttons.css

scrollable-buttons.css

241 ms

scrollable-horizontal.css

scrollable-horizontal.css

234 ms

scrollable-navigation.css

scrollable-navigation.css

242 ms

dateskin.css

dateskin.css

325 ms

chosen.css

chosen.css

335 ms

all.css

all.css

44 ms

elliswhittam.css

elliswhittam.css

339 ms

sm-core-css.css

sm-core-css.css

335 ms

sm-mint.css

sm-mint.css

343 ms

email-decode.min.js

email-decode.min.js

236 ms

rocket-loader.min.js

rocket-loader.min.js

241 ms

SearchIcon2.png

SearchIcon2.png

341 ms

FODO-logo.png

FODO-logo.png

464 ms

UPHVPISZNN_Patient_and_Public.png

UPHVPISZNN_Patient_and_Public.png

440 ms

URJXRKU1PP_Policymakers.png

URJXRKU1PP_Policymakers.png

428 ms

90IY7H4G69_Members.png

90IY7H4G69_Members.png

434 ms

J9S8GQDQGJ_News_and_Views.png

J9S8GQDQGJ_News_and_Views.png

441 ms

C91F82BJ76_FODO_Banner_2020.jpg

C91F82BJ76_FODO_Banner_2020.jpg

707 ms

FODOBanner.jpg

FODOBanner.jpg

525 ms

FODOPrincipleBannerMobile.png

FODOPrincipleBannerMobile.png

599 ms

fodobanner.png

fodobanner.png

635 ms

linkedinwhite.png

linkedinwhite.png

543 ms

twitterwhite.png

twitterwhite.png

561 ms

FODO-logo-white.png

FODO-logo-white.png

627 ms

masterv5.css

masterv5.css

533 ms

custom-css.css

custom-css.css

539 ms

module.css

module.css

105 ms

rhs.css

rhs.css

105 ms

css

css

17 ms

campaigns.css

campaigns.css

100 ms

_tx_.gif

_tx_.gif

206 ms

92 ms

logobackdrop.png

logobackdrop.png

123 ms

logobackdrop1.png

logobackdrop1.png

122 ms

Join-background.gif

Join-background.gif

452 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff

17 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

30 ms

print.css

print.css

102 ms

js

js

75 ms

loader.js

loader.js

20 ms

jquery-2.1.3.js

jquery-2.1.3.js

145 ms

jquery.tools.min.js

jquery.tools.min.js

108 ms

Accessibility Review

fodo.com accessibility score

86

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

SEO Factors

fodo.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fodo.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fodo.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

fodo.com

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