Tools & Wizards About Us
eiendo.com screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

eiendo.com

Eastern Iowa Endodontics | Board-Certified Endodontist

Page Load Speed

2.8 sec in total

First Response

72 ms

Resources Loaded

2 sec

Page Rendered

751 ms

eiendo.com screenshot

About Website

Visit eiendo.com now to see the best up-to-date Eiendo content and also check out these interesting facts you probably never knew about eiendo.com

At Eastern Iowa Endodontics, our Cedar Rapids board-certified endodontist specializes in root canal treatment. We provide the best care.

Visit eiendo.com

Key Findings

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

Performance Metrics

eiendo.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value14.2 s

0/100

25%

SI (Speed Index)

Value5.7 s

50/100

10%

TBT (Total Blocking Time)

Value880 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value11.0 s

20/100

10%

Network Requests Diagram

eiendo.com

72 ms

eiendo.com

166 ms

bcf20799580c56ea17e8996bc63aeccd.css

175 ms

jquery.min.js

146 ms

css

31 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 80% of them (36 requests) were addressed to the original Eiendo.com, 7% (3 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Birdeye.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 256.5 kB (9%)

Content Size

2.8 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-82%

Potential reduce by 78.5 kB

  • Original 95.2 kB
  • After minification 91.9 kB
  • After compression 16.7 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 78.5 kB or 82% of the original size.

Image Optimization

-7%

Potential reduce by 177.8 kB

  • Original 2.7 MB
  • After minification 2.5 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. Eiendo images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 94 B

  • Original 22.3 kB
  • After minification 22.3 kB
  • After compression 22.2 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.

Requests Breakdown

Number of requests can be reduced by 11 (28%)

Requests Now

40

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eiendo.com

eiendo.com

72 ms

eiendo.com

eiendo.com

166 ms

bcf20799580c56ea17e8996bc63aeccd.css

bcf20799580c56ea17e8996bc63aeccd.css

175 ms

jquery.min.js

jquery.min.js

146 ms

css

css

31 ms

js

js

61 ms

js

js

109 ms

1234669090094

1234669090094

1759 ms

seal.js

seal.js

94 ms

wp-polyfill.min.js

wp-polyfill.min.js

79 ms

hooks.min.js

hooks.min.js

92 ms

i18n.min.js

i18n.min.js

105 ms

lazyload.min.js

lazyload.min.js

103 ms

5dc1d8ef90fcdf3bfe79f41810145346.js

5dc1d8ef90fcdf3bfe79f41810145346.js

484 ms

HPHero2.jpg

HPHero2.jpg

267 ms

afterh1.png

afterh1.png

124 ms

wave_whiteonbottom.png

wave_whiteonbottom.png

123 ms

wave_whiteontop.png

wave_whiteontop.png

125 ms

HPtestimonials.jpg

HPtestimonials.jpg

428 ms

js

js

81 ms

analytics.js

analytics.js

78 ms

Stars.png

Stars.png

75 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

166 ms

fa-solid-900.woff

fa-solid-900.woff

163 ms

fa-regular-400.woff

fa-regular-400.woff

107 ms

collect

collect

81 ms

eastern-iowa-endodontics-32121051.png

eastern-iowa-endodontics-32121051.png

138 ms

EIENDOLogo.png

EIENDOLogo.png

39 ms

logo.png

logo.png

62 ms

logo_black.png

logo_black.png

53 ms

MobileHPimg1.jpg

MobileHPimg1.jpg

83 ms

HPimg1.jpg

HPimg1.jpg

182 ms

Gentlewave2.png

Gentlewave2.png

76 ms

NEW-GENTLEWAVE-AUTHORIZED-PRACTICE-COLOR-460x180.png

NEW-GENTLEWAVE-AUTHORIZED-PRACTICE-COLOR-460x180.png

141 ms

RCAG.png

RCAG.png

133 ms

afterh1transparent.png

afterh1transparent.png

132 ms

Specialist.png

Specialist.png

141 ms

BoardCert.png

BoardCert.png

142 ms

USDVA.png

USDVA.png

156 ms

EIENDOLogoWhite-300x191.png

EIENDOLogoWhite-300x191.png

188 ms

Image20230914105342.png

Image20230914105342.png

210 ms

BBB.png

BBB.png

180 ms

BirdEye.png

BirdEye.png

188 ms

NEW-GENTLEWAVE-AUTHORIZED-PRACTICE-COLORfooter.png

NEW-GENTLEWAVE-AUTHORIZED-PRACTICE-COLORfooter.png

192 ms

visa-mastercard-andmore-logo.png

visa-mastercard-andmore-logo.png

219 ms

Accessibility Review

eiendo.com accessibility score

72

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

eiendo.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

eiendo.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

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

eiendo.com

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