Tools & Wizards About Us
edatasource.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

edatasource.com

eDataSource | Email Deliverability & Performance Optimization

Page Load Speed

3.6 sec in total

First Response

67 ms

Resources Loaded

1.9 sec

Page Rendered

1.6 sec

edatasource.com screenshot

About Website

Visit edatasource.com now to see the best up-to-date EDataSource content for United States and also check out these interesting facts you probably never knew about edatasource.com

eDataSource is the premier source of email deliverability technology and performance insights with the most expansive data coverage in the industry.

Visit edatasource.com

Key Findings

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

Performance Metrics

edatasource.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value22.3 s

0/100

25%

SI (Speed Index)

Value17.1 s

0/100

10%

TBT (Total Blocking Time)

Value3,890 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.154

75/100

15%

TTI (Time to Interactive)

Value28.4 s

0/100

10%

Network Requests Diagram

edatasource.com

67 ms

style.min.css

36 ms

swiper-bundle.min.css

92 ms

font-awesome.min.css

45 ms

style.min.css

51 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 61% of them (72 requests) were addressed to the original Edatasource.com, 4% (5 requests) were made to Player.vimeo.com and 4% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (973 ms) belongs to the original domain Edatasource.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (30%)

Content Size

4.2 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 198.6 kB

  • Original 236.3 kB
  • After minification 225.1 kB
  • After compression 37.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 198.6 kB or 84% of the original size.

Image Optimization

-29%

Potential reduce by 1.1 MB

  • Original 3.7 MB
  • After minification 2.6 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. Obviously, EDataSource needs image optimization as it can save up to 1.1 MB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 1.5 kB

  • Original 281.9 kB
  • After minification 281.9 kB
  • After compression 280.3 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

-2%

Potential reduce by 20 B

  • Original 1.3 kB
  • After minification 1.3 kB
  • After compression 1.3 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. Edatasource.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 51 (49%)

Requests Now

105

After Optimization

54

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

edatasource.com

edatasource.com

67 ms

style.min.css

style.min.css

36 ms

swiper-bundle.min.css

swiper-bundle.min.css

92 ms

font-awesome.min.css

font-awesome.min.css

45 ms

style.min.css

style.min.css

51 ms

animate.css

animate.css

47 ms

jyc0wtl.css

jyc0wtl.css

171 ms

style.css

style.css

51 ms

supplimental.css

supplimental.css

64 ms

style-static.min.css

style-static.min.css

103 ms

style.css

style.css

73 ms

style.css

style.css

81 ms

jquery.min.js

jquery.min.js

133 ms

jquery-migrate.min.js

jquery-migrate.min.js

133 ms

sfwp2l.css

sfwp2l.css

129 ms

navigation.js

navigation.js

130 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

132 ms

jquery.main.js

jquery.main.js

142 ms

scripts.min.js

scripts.min.js

157 ms

common.js

common.js

137 ms

swiper-bundle.min.js

swiper-bundle.min.js

154 ms

splc-script.min.js

splc-script.min.js

148 ms

jquery.cookies.js

jquery.cookies.js

156 ms

cp-submit-actions.js

cp-submit-actions.js

199 ms

cp-video-api.js

cp-video-api.js

177 ms

cp-popup.js

cp-popup.js

186 ms

api.js

api.js

36 ms

jquery.fitvids.js

jquery.fitvids.js

181 ms

easypiechart.js

easypiechart.js

470 ms

p.css

p.css

40 ms

gtm.js

gtm.js

305 ms

281858136

281858136

433 ms

Decision2020_blog-356x200.jpg

Decision2020_blog-356x200.jpg

262 ms

Black_Friday_2019-356x200.jpg

Black_Friday_2019-356x200.jpg

262 ms

deliver.png

deliver.png

611 ms

salesforce-logo-full.png

salesforce-logo-full.png

261 ms

deg-logo-full.png

deg-logo-full.png

263 ms

mintel-logo-full.png

mintel-logo-full.png

261 ms

inboxlabs-logo-full-2.png

inboxlabs-logo-full-2.png

517 ms

goldstar-logo-full.png

goldstar-logo-full.png

504 ms

Zillow-logo-full.png

Zillow-logo-full.png

504 ms

Verabradley_logo-full.png

Verabradley_logo-full.png

504 ms

teleflora-logo-full.png

teleflora-logo-full.png

505 ms

swatch-logo-full.png

swatch-logo-full.png

581 ms

sparkpost-logo-full-2.png

sparkpost-logo-full-2.png

620 ms

SGTwilio-logo-full-2.png

SGTwilio-logo-full-2.png

559 ms

ScottsMG-logo-full.png

ScottsMG-logo-full.png

558 ms

priceline-logo-full.png

priceline-logo-full.png

581 ms

hennessy-logo-full.png

hennessy-logo-full.png

619 ms

merkle-logo-full.png

merkle-logo-full.png

619 ms

match-logo-full-2.png

match-logo-full-2.png

672 ms

fender-full.png

fender-full.png

670 ms

1800-flowers-full-2.png

1800-flowers-full-2.png

674 ms

hotchalk-logo-full.png

hotchalk-logo-full.png

754 ms

publishers-clearing-house-logo-full.png

publishers-clearing-house-logo-full.png

755 ms

computer_mockup-burst.png

computer_mockup-burst.png

782 ms

mac.png

mac.png

755 ms

minisample2_opt.jpg

minisample2_opt.jpg

758 ms

minisample_comptrack.jpg

minisample_comptrack.jpg

764 ms

minisample3_opt.jpg

minisample3_opt.jpg

808 ms

strategy_frame2.png

strategy_frame2.png

928 ms

BetterTogether_2000x1125-356x200.jpg

BetterTogether_2000x1125-356x200.jpg

806 ms

Holiday_Preview_blog-356x200.jpg

Holiday_Preview_blog-356x200.jpg

807 ms

bg-page.jpg

bg-page.jpg

973 ms

mmmaawg_logo.png

mmmaawg_logo.png

908 ms

314833129

314833129

574 ms

314846169

314846169

507 ms

314830581

314830581

493 ms

d

d

300 ms

d

d

313 ms

d

d

332 ms

fa-brands-400.woff

fa-brands-400.woff

785 ms

fa-regular-400.woff

fa-regular-400.woff

704 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

707 ms

d

d

343 ms

recaptcha__en.js

recaptcha__en.js

427 ms

fa-solid-900.woff

fa-solid-900.woff

680 ms

icomoon.ttf

icomoon.ttf

718 ms

eds_watermark-500x383.png

eds_watermark-500x383.png

679 ms

281858136

281858136

342 ms

analytics.js

analytics.js

130 ms

destination

destination

90 ms

fbevents.js

fbevents.js

147 ms

hotjar-541037.js

hotjar-541037.js

266 ms

insight.min.js

insight.min.js

146 ms

uwt.js

uwt.js

179 ms

conversion_async.js

conversion_async.js

266 ms

loader.js

loader.js

183 ms

756530819-85f09a693a51a6979c4f0a191c7c26851de708149b40f55c1fa385cdbe5486e4-d

756530819-85f09a693a51a6979c4f0a191c7c26851de708149b40f55c1fa385cdbe5486e4-d

677 ms

756533422-f9c884f8dbbc6503b6539be49ed82f3501a0e3c966f96721535fd781d2436e0f-d

756533422-f9c884f8dbbc6503b6539be49ed82f3501a0e3c966f96721535fd781d2436e0f-d

515 ms

collect

collect

41 ms

756461055-84a5a7da8295dfd42303de055a56292cfaf0f911d8ad2cc6a1e1d0ea059f394d-d

756461055-84a5a7da8295dfd42303de055a56292cfaf0f911d8ad2cc6a1e1d0ea059f394d-d

170 ms

insight_tag_errors.gif

insight_tag_errors.gif

308 ms

collect

collect

256 ms

js

js

132 ms

fallback

fallback

77 ms

fallback

fallback

182 ms

call-tracking_9.js

call-tracking_9.js

36 ms

715712591-9f855b3cc27d17460e78de18161918dac4b9773d75f91cecbe86d8ebd5be4afd-d

715712591-9f855b3cc27d17460e78de18161918dac4b9773d75f91cecbe86d8ebd5be4afd-d

161 ms

adsct

adsct

277 ms

adsct

adsct

266 ms

modules.404c8789d11e259a4872.js

modules.404c8789d11e259a4872.js

172 ms

wcm

wcm

125 ms

fallback__ltr.css

fallback__ltr.css

108 ms

css

css

91 ms

ga-audiences

ga-audiences

44 ms

cp-popup.css

cp-popup.css

103 ms

logo_48.png

logo_48.png

2 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

28 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

32 ms

pd.js

pd.js

21 ms

pp8czxqt

pp8czxqt

33 ms

close1.png

close1.png

35 ms

close5.png

close5.png

40 ms

notification_alert.png

notification_alert.png

63 ms

quote-left.png

quote-left.png

41 ms

quote-right.png

quote-right.png

32 ms

analytics

analytics

25 ms

Accessibility Review

edatasource.com accessibility score

86

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.

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

High

ARIA IDs are not unique

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

edatasource.com best practices score

75

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

Browser errors were logged to the console

SEO Factors

edatasource.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 Edatasource.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 Edatasource.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

edatasource.com

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