1.8 sec in total
286 ms
990 ms
539 ms
Visit lafayetteeye.com now to see the best up-to-date Lafayette Eye content and also check out these interesting facts you probably never knew about lafayetteeye.com
We offer quality eye care in Lafayette Hill, Germantown, Blue Bell, Plymouth Meeting, Conshohocken and Roxborough communities. Call or text (610) 825-3937.
Visit lafayetteeye.comWe analyzed Lafayetteeye.com page load time and found that the first response time was 286 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
lafayetteeye.com performance score
name
value
score
weighting
Value2.0 s
83/100
10%
Value2.4 s
92/100
25%
Value12.1 s
3/100
10%
Value1,350 ms
17/100
30%
Value0.025
100/100
15%
Value11.5 s
18/100
10%
286 ms
21 ms
129 ms
29 ms
4 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 26% of them (11 requests) were addressed to the original Lafayetteeye.com, 42% (18 requests) were made to Cdcssl.ibsrv.net and 9% (4 requests) were made to Apps.imatrixbase.com. The less responsive or slowest element that took the longest time to load (452 ms) relates to the external source Smbleads.ibsmb.com.
Page size can be reduced by 338.1 kB (35%)
972.7 kB
634.6 kB
In fact, the total size of Lafayetteeye.com main page is 972.7 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. 70% of websites need less resources to load. Javascripts take 703.2 kB which makes up the majority of the site volume.
Potential reduce by 157.6 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 157.6 kB or 80% of the original size.
Potential reduce by 86 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. Lafayette Eye images are well optimized though.
Potential reduce by 180.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 180.4 kB or 26% of the original size.
Potential reduce by 0 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.
Number of requests can be reduced by 17 (41%)
41
24
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lafayette 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 18 to 1 for JavaScripts and as a result speed up the page load time.
lafayetteeye.com
286 ms
709417d9806ecc253a54fc70e453587d.opt-min.cr.js
21 ms
29a75db7a89c9a5e6fa3c2cba5fe67d1.opt-min.cr.css
129 ms
css2
29 ms
email-decode.min.js
4 ms
jquery-1.11.1.min.js
15 ms
smb-number-changer.js
149 ms
masonry.pkgd.min.js
37 ms
js
67 ms
widget2.5f7299ac.js
54 ms
smb-number-changer.js
166 ms
8e0ad76800efb2aec3df15e86c7dc751.opt-min.co.js
29 ms
js-defer.js
149 ms
logo_tag_dark.png.webp
121 ms
LimelightButtonsv2-14.png
341 ms
location-search.png
80 ms
icon-back-to-top.png
79 ms
5f527a5330be0_facebook.png.webp
80 ms
5f527a782b68d_googlehangouts.png.webp
163 ms
5f527aa97b454_instagramsketched.png.webp
94 ms
text-to-call-icon-resized.png.webp
92 ms
6351e5adb9444_slider04.jpg.webp
198 ms
shutterstock_2125662620.jpg.webp
197 ms
sunglass-regular-1.jpg.webp
197 ms
2137545377.jpg.webp
104 ms
1g.jpg.webp
106 ms
6351e60f37fef_blade01.jpg.webp
203 ms
6349a1be88f5a_blade2.jpg.webp
140 ms
60ba3b6663b0d_banner.jpg.webp
152 ms
61f18db7517c8_60ba42c04814bdrkulich.jpg.webp
244 ms
61f18dc7592b8_60ba4326c0264sp2.jpg.webp
253 ms
60ba391a317f6_img00351.jpg.webp
198 ms
60ba3aeda5656_unnamed3.jpg.webp
197 ms
RevolutionPHR.png.webp
275 ms
5n9HLjNxjI94N3BjHcDZjL9m
452 ms
jquery-1.11.1.min.js
133 ms
javascript,window.pagespeed.psatemp%3D0%3B
0 ms
smb-number-changer.js
20 ms
masonry.pkgd.min.js
19 ms
js
30 ms
widget2.5f7299ac.js
21 ms
smb-number-changer.js
20 ms
8e0ad76800efb2aec3df15e86c7dc751.opt-min.co.js
24 ms
lafayetteeye.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
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
Links do not have a discernible name
lafayetteeye.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
lafayetteeye.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lafayetteeye.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 Lafayetteeye.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.
lafayetteeye.com
Open Graph data is detected on the main page of Lafayette Eye. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: