2.2 sec in total
171 ms
1.3 sec
681 ms
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.comWe analyzed Thomaseye.com page load time and found that the first response time was 171 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
thomaseye.com performance score
name
value
score
weighting
Value2.8 s
57/100
10%
Value2.8 s
84/100
25%
Value2.8 s
96/100
10%
Value450 ms
63/100
30%
Value0.003
100/100
15%
Value9.6 s
30/100
10%
171 ms
485 ms
63 ms
24 ms
43 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 67% of them (47 requests) were addressed to the original Thomaseye.com, 4% (3 requests) were made to Googletagmanager.com and 4% (3 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (487 ms) relates to the external source V2.mdidentity.com.
Page size can be reduced by 60.3 kB (8%)
732.4 kB
672.1 kB
In fact, the total size of Thomaseye.com main page is 732.4 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. 60% of websites need less resources to load. Images take 569.2 kB which makes up the majority of the site volume.
Potential reduce by 59.9 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 59.9 kB or 77% of the original size.
Potential reduce by 33 B
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.
Potential reduce by 303 B
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.
Potential reduce by 45 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. Thomaseye.com has all CSS files already compressed.
Number of requests can be reduced by 39 (61%)
64
25
The browser has sent 64 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 23 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
thomaseye.com
171 ms
www.thomaseye.com
485 ms
css2
63 ms
style.css
24 ms
style.css
43 ms
reset.css
52 ms
media_query.css
50 ms
megamenu.css
46 ms
content_slider.css
46 ms
jquery.min.js
65 ms
css_browser_selector.js
48 ms
megamenu_plugins.js
54 ms
megamenu.js
62 ms
contentfixer.js
62 ms
custom.js
56 ms
lazysizes.min.js
63 ms
content_slider.min.js
62 ms
js
164 ms
wowslider.js
160 ms
script.js
164 ms
6b7d7a77ad9a220ff042286e4d3563a3204448b6.js
229 ms
gtm.js
155 ms
fbevents.js
155 ms
22
487 ms
top_bg.jpg
130 ms
logo.png
129 ms
fb.jpg
130 ms
tw.jpg
199 ms
yt.jpg
130 ms
insta-header.jpg
129 ms
blog.jpg
228 ms
pay_icon.png
197 ms
phone_icon.png
198 ms
bullet.png
198 ms
map_shadow.png
197 ms
map.jpg
230 ms
patient_stories1.png
228 ms
videos1.png
227 ms
financing1.png
228 ms
footer_wrapper_bg.png
228 ms
footer_logo.jpg
264 ms
btn_arama_buton.jpg
231 ms
input_search.jpg
232 ms
Schedule-Online-Web-Banner.jpg
264 ms
retina.jpg
178 ms
family_eye_care3.jpg
223 ms
lasik.jpg
221 ms
Glaucoma2.jpg
223 ms
Cataracts2.jpg
262 ms
aesthetics.jpg
389 ms
pediatric-eye-care.jpg
387 ms
glasses-and-contacts.jpg
388 ms
bx_loader.gif
344 ms
controls.png
345 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff
130 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff
177 ms
conversion_async.js
300 ms
loader.js
168 ms
modules.js
126 ms
2378988115552389
125 ms
analytics.js
235 ms
js
104 ms
1623494834540470
62 ms
call-tracking_7.js
37 ms
93 ms
collect
42 ms
collect
39 ms
wcm
37 ms
22 ms
ga-audiences
24 ms
thomaseye.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
thomaseye.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
thomaseye.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
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 neither this language nor any other was claimed in <html> or <meta> tags. 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.
thomaseye.com
Open Graph description is not detected on the main page of Thomas Eye. 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: