Tools & Wizards About Us

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

thomaseye.com

Eye Doctors and Eye Care – Thomas Eye Group

Page Load Speed

980 ms in total

First Response

16 ms

Resources Loaded

692 ms

Page Rendered

272 ms

About Website

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

Thomas Eye Group, founded in 1974, offers several eye care services in the Greater Atlanta Area. Check out all our services.

Visit thomaseye.com

Key Findings

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

Performance Metrics

thomaseye.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

4/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value1,510 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.096

90/100

15%

TTI (Time to Interactive)

Value13.8 s

10/100

10%

Network Requests Diagram

thomaseye.com

16 ms

www.thomaseye.com

108 ms

css

31 ms

a11y-toolbar.css

10 ms

a11y.css

22 ms

Our browser made a total of 113 requests to load all elements on the main page. We found that 71% of them (80 requests) were addressed to the original Thomaseye.com, 24% (27 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (308 ms) belongs to the original domain Thomaseye.com.

Page Optimization Overview & Recommendations

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

Content Size

1.1 MB

After Optimization

956.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Thomaseye.com main page is 1.1 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. 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. Javascripts take 612.7 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 123.5 kB

  • Original 146.8 kB
  • After minification 143.9 kB
  • After compression 23.3 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 123.5 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 225.3 kB
  • After minification 225.3 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. Thomas Eye images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 2.1 kB

  • Original 612.7 kB
  • After minification 612.5 kB
  • After compression 610.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. This website has mostly compressed JavaScripts.

CSS Optimization

-4%

Potential reduce by 3.6 kB

  • Original 100.4 kB
  • After minification 98.0 kB
  • After compression 96.8 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. Thomaseye.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 67 (85%)

Requests Now

79

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

thomaseye.com accessibility score

96

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.

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

Links do not have a discernible name

Best Practices

thomaseye.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

thomaseye.com SEO score

84

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

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

High

Tap targets are not sized appropriately

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

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