Tools & Wizards About Us
mad.ly screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

mad.ly

Mad Mimi Email Marketing: Create, Send, And Track HTML Email Newsletters

Page Load Speed

1.2 sec in total

First Response

183 ms

Resources Loaded

836 ms

Page Rendered

157 ms

mad.ly screenshot

About Website

Welcome to mad.ly homepage info - get ready to check Mad best content for United States right away, or after learning these important things about mad.ly

Mad Mimi makes it simple to send HTML email newsletters, grow your subscribers and manage your email list. Sign up today!

Visit mad.ly

Key Findings

We analyzed Mad.ly page load time and found that the first response time was 183 ms and then it took 993 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

mad.ly performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value1,350 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value20.2 s

2/100

10%

Network Requests Diagram

mad.ly

183 ms

madmimi.com

115 ms

shag.css

5 ms

uxcore2.min.css

114 ms

appheader.min.css

105 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Mad.ly, 31% (9 requests) were made to D1lggihq2bt4jo.cloudfront.net and 28% (8 requests) were made to D2vnkn0bfhsarv.cloudfront.net. The less responsive or slowest element that took the longest time to load (384 ms) relates to the external source D2vnkn0bfhsarv.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 MB (66%)

Content Size

3.4 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mad.ly main page is 3.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 33.3 kB

  • Original 49.5 kB
  • After minification 47.0 kB
  • After compression 16.3 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 33.3 kB or 67% of the original size.

Image Optimization

-1%

Potential reduce by 906 B

  • Original 125.2 kB
  • After minification 124.3 kB

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. Mad images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 1.8 MB

  • Original 2.7 MB
  • After minification 2.7 MB
  • After compression 909.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.8 MB or 66% of the original size.

CSS Optimization

-77%

Potential reduce by 402.0 kB

  • Original 522.9 kB
  • After minification 520.1 kB
  • After compression 120.8 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. Mad.ly needs all CSS files to be minified and compressed as it can save up to 402.0 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (58%)

Requests Now

26

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mad.ly

mad.ly

183 ms

madmimi.com

madmimi.com

115 ms

shag.css

shag.css

5 ms

uxcore2.min.css

uxcore2.min.css

114 ms

appheader.min.css

appheader.min.css

105 ms

theme_madmimi-c20d560e277466f815880ebb2f11a26bb3e79d9b83c52fe02b5d04aa40e4e82f.css

theme_madmimi-c20d560e277466f815880ebb2f11a26bb3e79d9b83c52fe02b5d04aa40e4e82f.css

125 ms

application_home-8c0c8d36312dfad352bc30d0a8dbe296105df17d1d9f6acf058112b09d314c66.css

application_home-8c0c8d36312dfad352bc30d0a8dbe296105df17d1d9f6acf058112b09d314c66.css

142 ms

api.js

api.js

124 ms

modernizr.min-3414b046982d5eff0e0694d091076291c89da7d78bffbc408ab2548b19c7d88a.js

modernizr.min-3414b046982d5eff0e0694d091076291c89da7d78bffbc408ab2548b19c7d88a.js

122 ms

video-451f5da4b144775babfce02a350f40ed4b897edda3ace304f1d28002d1189489.js

video-451f5da4b144775babfce02a350f40ed4b897edda3ace304f1d28002d1189489.js

112 ms

i18n-base-ec72bdb37f15e5ca29dc7d10419a2e32ccb3dfe64ad4ac752d756d0cb334514f.js

i18n-base-ec72bdb37f15e5ca29dc7d10419a2e32ccb3dfe64ad4ac752d756d0cb334514f.js

110 ms

en-fcd220e0b0d0510c445ff43e1ba78303473e6bbe72f8ff8750ea5f94d7c78279.js

en-fcd220e0b0d0510c445ff43e1ba78303473e6bbe72f8ff8750ea5f94d7c78279.js

122 ms

uxcore2.min.js

uxcore2.min.js

106 ms

vendor.min.js

vendor.min.js

123 ms

heartbeat.js

heartbeat.js

121 ms

appheader.min.js

appheader.min.js

201 ms

application_non_webpack-df437c0613705fe15489663efd8362f7fd950c06532dcefcd1c78a7a8859b37e.js

application_non_webpack-df437c0613705fe15489663efd8362f7fd950c06532dcefcd1c78a7a8859b37e.js

209 ms

home-ab5257396966dc7a3b04c6968650428a61a19c5fc160745b1f3587b2c53c1670.js

home-ab5257396966dc7a3b04c6968650428a61a19c5fc160745b1f3587b2c53c1670.js

384 ms

recaptcha__en.js

recaptcha__en.js

277 ms

identity-c0e7156a45acfb4f778a527764c1a9e7b9fccd546c09504859106e108287a63d.png

identity-c0e7156a45acfb4f778a527764c1a9e7b9fccd546c09504859106e108287a63d.png

236 ms

bgdiag_opt-58fb87d3931991a2866c5160ca3fb63dee72e6d2cdbcdfc23274decfb557940d.svg

bgdiag_opt-58fb87d3931991a2866c5160ca3fb63dee72e6d2cdbcdfc23274decfb557940d.svg

240 ms

zig-ef0e5ba7922d93c4ca8dc5ae35e1a235f8afc48702abbf138e1faa5b8b77015f.png

zig-ef0e5ba7922d93c4ca8dc5ae35e1a235f8afc48702abbf138e1faa5b8b77015f.png

234 ms

mimiverse_social_feature@2x-548df911b2711960be2286eb4be26987578cb82076f4b6b5db597118348bbd8b.png

mimiverse_social_feature@2x-548df911b2711960be2286eb4be26987578cb82076f4b6b5db597118348bbd8b.png

238 ms

header_mimi_v2-d0643e9dfc5c549f389d072f8eff2b7533cc3efbb950154ab81e510c75fdd566.png

header_mimi_v2-d0643e9dfc5c549f389d072f8eff2b7533cc3efbb950154ab81e510c75fdd566.png

237 ms

thumb_home-ce11162dacd221e05fbead4a003bdf194c4b3800840f7e6cc5f619116200d9ec.png

thumb_home-ce11162dacd221e05fbead4a003bdf194c4b3800840f7e6cc5f619116200d9ec.png

237 ms

mimiverse_create_feature@2x-ebcc81411342835fad820d301f47da0070e605589f09de22abf9136bb0281923.png

mimiverse_create_feature@2x-ebcc81411342835fad820d301f47da0070e605589f09de22abf9136bb0281923.png

234 ms

mimiverse_stats_feature@2x-baf02bf1adf44ed21a77e211e8c97bbb7b7b78bd76e45c9987c44f957844bdef.png

mimiverse_stats_feature@2x-baf02bf1adf44ed21a77e211e8c97bbb7b7b78bd76e45c9987c44f957844bdef.png

237 ms

maawg_logo_sm-768522aaa56f75cf9adaa04a57e885353b8edbacec4e7eb776d8207426321c91.png

maawg_logo_sm-768522aaa56f75cf9adaa04a57e885353b8edbacec4e7eb776d8207426321c91.png

239 ms

shag.woff

shag.woff

51 ms

Accessibility Review

mad.ly accessibility score

89

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

Links do not have a discernible name

High

<object> elements do not have alternate text

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

mad.ly best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

mad.ly SEO score

92

Search Engine Optimization Advices

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document uses plugins

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 Mad.ly 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 Mad.ly 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

mad.ly

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