Tools & Wizards About Us
exetereye.com screenshot

Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

exetereye.com

Boston Optometrist - Exeter Eye Associates - Dr. Jeff Norden

Page Load Speed

1.2 sec in total

First Response

109 ms

Resources Loaded

836 ms

Page Rendered

271 ms

exetereye.com screenshot

About Website

Click here to check amazing Exeter Eye content. Otherwise, check out these important facts you probably never knew about exetereye.com

Dr. Jeff Norden has been practicing optometry in Boston, MA 02116, and surrounding areas for years. Call our office at 617-437-9995 to make an appointment today.

Visit exetereye.com

Key Findings

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

Performance Metrics

exetereye.com performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value21.1 s

0/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

exetereye.com

109 ms

exetereye.com

159 ms

ga.js

19 ms

jquery.js

38 ms

wowslider.js

70 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 82% of them (36 requests) were addressed to the original Exetereye.com, 5% (2 requests) were made to Ssl.google-analytics.com and 2% (1 request) were made to Botsrv.com. The less responsive or slowest element that took the longest time to load (415 ms) relates to the external source Botsrv.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 18.0 kB (1%)

Content Size

3.1 MB

After Optimization

3.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-72%

Potential reduce by 16.6 kB

  • Original 23.1 kB
  • After minification 20.6 kB
  • After compression 6.5 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 2.5 kB, which is 11% 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 16.6 kB or 72% of the original size.

Image Optimization

-0%

Potential reduce by 480 B

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

JavaScript Optimization

-0%

Potential reduce by 497 B

  • Original 109.9 kB
  • After minification 109.9 kB
  • After compression 109.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

-24%

Potential reduce by 345 B

  • Original 1.4 kB
  • After minification 1.4 kB
  • After compression 1.1 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. Exetereye.com needs all CSS files to be minified and compressed as it can save up to 345 B or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (16%)

Requests Now

38

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Exeter 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 7 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

exetereye.com

exetereye.com

109 ms

exetereye.com

exetereye.com

159 ms

ga.js

ga.js

19 ms

jquery.js

jquery.js

38 ms

wowslider.js

wowslider.js

70 ms

ajximagerotator.css

ajximagerotator.css

99 ms

style.css

style.css

100 ms

ajximagerotator1.css

ajximagerotator1.css

103 ms

ajximagerotator1.js

ajximagerotator1.js

102 ms

style.css

style.css

104 ms

QeWyGENR84EaLRj0

QeWyGENR84EaLRj0

415 ms

__utm.gif

__utm.gif

12 ms

counter.js

counter.js

35 ms

t.php

t.php

74 ms

top_bg.jpg

top_bg.jpg

33 ms

widget.js

widget.js

22 ms

424x68xlogo2.png.pagespeed.ic.qopcX8_VKm.png

424x68xlogo2.png.pagespeed.ic.qopcX8_VKm.png

66 ms

phone2.png

phone2.png

66 ms

menu.gif

menu.gif

37 ms

home.gif

home.gif

35 ms

menu_div.gif

menu_div.gif

35 ms

team.gif

team.gif

49 ms

office.gif

office.gif

68 ms

appointment.gif

appointment.gif

66 ms

patient_information.gif

patient_information.gif

68 ms

contact_us.gif

contact_us.gif

80 ms

flash1.jpg

flash1.jpg

128 ms

flash2.jpg

flash2.jpg

158 ms

flash3.jpg

flash3.jpg

194 ms

flash4.jpg

flash4.jpg

162 ms

new-office2.png

new-office2.png

99 ms

content_bg.jpg

content_bg.jpg

111 ms

content.jpg

content.jpg

335 ms

middle_boxes.gif

middle_boxes.gif

142 ms

clarifye.jpg

clarifye.jpg

160 ms

click.png

click.png

175 ms

appointment.png

appointment.png

189 ms

appt.png

appt.png

192 ms

facebook.jpg

facebook.jpg

194 ms

onesight.png

onesight.png

237 ms

lc.png

lc.png

220 ms

optomap.png

optomap.png

223 ms

widget_app_base_1730455764190.js

widget_app_base_1730455764190.js

178 ms

widget2.08973ec1.min.js

widget2.08973ec1.min.js

52 ms

Accessibility Review

exetereye.com accessibility score

85

Accessibility Issues

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

exetereye.com best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

exetereye.com SEO score

69

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Exetereye.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 Exetereye.com main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

exetereye.com

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