Skip to content
https://mailenable.com

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

88

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
mailenable.com/images/home_banner_sprite.jpg259200.0 s360.2 KiB
/signals/config/1489296768042405?v=2.9.303&r=stable&domai...1200.0 s44.7 KiB
mailenable.com/css/mev5.css259200.0 s124.0 KiB
mailenable.com/images/footer_partners.jpg259200.0 s27.9 KiB
mailenable.com/images/home_bot_banner_v9.jpg259200.0 s24.8 KiB
mailenable.com/css/mev5_base.css259200.0 s21.8 KiB
mailenable.com/images/home_banner01.jpg259200.0 s17.4 KiB
mailenable.com/images/bttn_video_tutes.jpg259200.0 s17.0 KiB
mailenable.com/Library/Scripts/SlidesJS.js259200.0 s14.7 KiB
mailenable.com/images/bttn_webmail_demo.jpg259200.0 s13.5 KiB
mailenable.com/images/ajax-loader-bar.gif259200.0 s10.8 KiB
mailenable.com/images/footNav_follow_icons.png259200.0 s7.9 KiB
mailenable.com/images/topNav_logo.png259200.0 s5.2 KiB
mailenable.com/Library/Scripts/superfish.js259200.0 s5.2 KiB
mailenable.com/images/icon_pack.png259200.0 s4.1 KiB
mailenable.com/images/slidesjs_topBanner_arrows.png259200.0 s3.9 KiB
mailenable.com/images/head_latestNews.png259200.0 s3.8 KiB
mailenable.com/images/slidesjs_topBanner_pagination.png259200.0 s1.7 KiB
mailenable.com/images/icon_products.png259200.0 s1.5 KiB
mailenable.com/images/level0_shell_bg.jpg259200.0 s747 B
mailenable.com/images/home_banner_shadow.jpg259200.0 s585 B
mailenable.com/images/icon_arrows.gif259200.0 s468 B
mailenable.com/images/icon_tick_green.gif259200.0 s409 B
mailenable.com/images/icon_arrow_blue.gif259200.0 s368 B
/tr/?id=1489296768042405&ev=PageView&dl=https%3A%2F%2Fmai...0.0 ms19 B

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:21.092 source:map[column:30177 line:2 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.11.1/jquery.min.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:15.698 source:map[type:text value:[unattributed]]] map[reflowTime:10.478 source:map[column:31201 line:1 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.11.1/jquery.min.js urlProvider:network]] map[reflowTime:5.852 source:map[column:24687 line:2 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.11.1/jquery.min.js urlProvider:network]] map[reflowTime:2.188 source:map[column:24384 line:2 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.11.1/jquery.min.js urlProvider:network]] map[reflowTime:2.574 source:map[column:28786 line:2 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.11.1/jquery.min.js urlProvider:network]]]

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLProtocol
mailenable.com/http/1.1
mailenable.com/css/mev5_base.csshttp/1.1
mailenable.com/css/mev5.csshttp/1.1
mailenable.com/Library/Scripts/superfish.jshttp/1.1
mailenable.com/Library/Scripts/SlidesJS.jshttp/1.1
mailenable.com/images/level0_shell_bg.jpghttp/1.1
mailenable.com/images/topNav_logo.pnghttp/1.1
mailenable.com/images/icon_pack.pnghttp/1.1
mailenable.com/images/home_banner01.jpghttp/1.1
mailenable.com/images/ajax-loader-bar.gifhttp/1.1
mailenable.com/images/bttn_video_tutes.jpghttp/1.1
mailenable.com/images/bttn_webmail_demo.jpghttp/1.1
mailenable.com/images/head_latestNews.pnghttp/1.1
mailenable.com/images/home_banner_shadow.jpghttp/1.1
mailenable.com/images/icon_products.pnghttp/1.1
mailenable.com/images/icon_arrows.gifhttp/1.1
mailenable.com/images/icon_arrow_blue.gifhttp/1.1
mailenable.com/images/icon_tick_green.gifhttp/1.1
mailenable.com/images/home_bot_banner_v9.jpghttp/1.1
mailenable.com/images/footer_partners.jpghttp/1.1
mailenable.com/images/footNav_follow_icons.pnghttp/1.1
mailenable.com/images/home_banner_sprite.jpghttp/1.1
mailenable.com/images/slidesjs_topBanner_arrows.pnghttp/1.1
mailenable.com/images/slidesjs_topBanner_pagination.pnghttp/1.1
mailenable.com/favicon.icohttp/1.1

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer SizeDuration
mailenable.com/Library/Scripts/SlidesJS.js14.7 KiB596 ms
mailenable.com/css/mev5_base.css21.8 KiB155 ms
mailenable.com/Library/Scripts/superfish.js5.2 KiB449 ms
mailenable.com/css/mev5.css124.0 KiB890 ms
fonts.googleapis.com/css?family=Roboto:900|Roboto+Slab:700|Muli:3002.3 KiB265 ms
www.googleadservices.com/pagead/conversion.js23.6 KiB466 ms
ajax.googleapis.com/ajax/libs/jquery/1.11.1/jquery.min.js33.3 KiB329 ms

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
div#slides > div.slidesjs-container > div.slidesjs-control > div.slide_content div#slides > div.slidesjs-container > div.slidesjs-control > div.slide_content
mailenable.com/images/home_banner_sprite.jpg360.0 KiB211.9 KiB
Hosting Controller div.level0_shell > div.level1_shell > div.foot_partners_shell > div.foot_partners
mailenable.com/images/footer_partners.jpg27.6 KiB18.7 KiB
MailEnable 10 Now Available... More Info div.level1_shell > div.body_shell > div.body_3Col > div.home_banner_botRight
mailenable.com/images/home_bot_banner_v9.jpg24.5 KiB13.1 KiB
NEW! View Online Video Tutorials div.level1_shell > div.home_banner_shell > div.home_banner_demo_shell > div#banner_demo_1
mailenable.com/images/bttn_video_tutes.jpg16.8 KiB8.7 KiB
Follow Us div.level1_shell > div.footNav_shell > div.footNav_follow_shell > div.footNav_follow
mailenable.com/images/footNav_follow_icons.png7.6 KiB5.3 KiB
  div.level0_shell > div.level1_shell > div.topNav_shell > div.topNav_logo
mailenable.com/images/topNav_logo.png4.9 KiB4.0 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 290 ms 126.5 KiB
URLTransfer SizeEst Savings
mailenable.com/css/mev5.css123.8 KiB115.0 KiB
mailenable.com/css/mev5_base.css21.5 KiB11.5 KiB

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 26.9 KiB
URLTransfer SizeEst Savings
mailenable.com/css/mev5.css124.0 KiB22.0 KiB
mailenable.com/css/mev5_base.css21.8 KiB5.0 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 342.5 KiB
URLTransfer SizeEst Savings
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js361.8 KiB242.2 KiB
www.googletagmanager.com/gtag/js?id=G-LSTDXPQP2M164.2 KiB66.1 KiB
connect.facebook.net/en_US/fbevents.js96.5 KiB34.3 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits
●Optimize DOM size
●Font display
●LCP breakdown
●Optimize viewport for mobile
●Max Potential First Input Delay 60 ms
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,435 KiB
●User Timing marks and measures 5 user timings
●JavaScript execution time 0.2 s
●Minimizes main-thread work 0.5 s
●Avoid long main-thread tasks 2 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 110 ms
●Server Backend Latencies 170 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 110 ms
○INP breakdown
○LCP request discovery
○Avoid non-composited animations
○Avoid large layout shifts
46

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.topNav_search_shell > div.topNav_search > form#searchForm > input#site_search div.topNav_search_shell > div.topNav_search > form#searchForm > input#site_search
independent survey div.level1_shell > div.body_shell > div.body_3Col_2span > a
MailEnable 10 div.level1_shell > div.body_shell > div.body_3Col_2span > a
Version 10 div.level1_shell > div.body_shell > div.body_3Col_2span > a

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Our Mailing List div.level1_shell > div.body_shell > div.body_3Col > h3

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.topNav_search_shell > div.topNav_search > form#searchForm > input#site_search div.topNav_search_shell > div.topNav_search > form#searchForm > input#site_search
div.home_subscribe_shell > form > div.home_subscribe_input > input#email div.home_subscribe_shell > form > div.home_subscribe_input > input#email

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
  div.level1_shell > div.topNav_shell > div.topNav_logo > a
div.slidesjs-container > div.slidesjs-control > div.slide_content > a.canvas_bttn div.slidesjs-container > div.slidesjs-control > div.slide_content > a.canvas_bttn
div.slidesjs-container > div.slidesjs-control > div.slide_content > a.canvas_bttn div.slidesjs-container > div.slidesjs-control > div.slide_content > a.canvas_bttn
div.slidesjs-container > div.slidesjs-control > div.slide_content > a.canvas_bttn div.slidesjs-container > div.slidesjs-control > div.slide_content > a.canvas_bttn

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 div#slides > ul.slidesjs-pagination > li.slidesjs-pagination-item > a.active
2 div#slides > ul.slidesjs-pagination > li.slidesjs-pagination-item > a
3 div#slides > ul.slidesjs-pagination > li.slidesjs-pagination-item > a
4 div#slides > ul.slidesjs-pagination > li.slidesjs-pagination-item > a
5 div#slides > ul.slidesjs-pagination > li.slidesjs-pagination-item > a
Download div.home_products_right > ul > li > a
More info div.home_products_right > ul > li > a
Free Trial div.home_products_right > ul > li > a
More info div.home_products_right > ul > li > a
Free Trial div.home_products_right > ul > li > a
More info div.home_products_right > ul > li > a
Free Trial div.home_products_right > ul > li > a
More info div.home_products_right > ul > li > a
Overview div.footNav_shell > ul > li > a
Features div.footNav_shell > ul > li > a
Comparisons div.footNav_shell > ul > li > a
Solutions div.footNav_shell > ul > li > a
Product Editions div.footNav_shell > ul > li > a
Feature Matrix div.footNav_shell > ul > li > a
Webmail Demo div.footNav_shell > ul > li > a
Video Gallery div.footNav_shell > ul > li > a
Pricing div.footNav_shell > ul > li > a
Upgrades div.footNav_shell > ul > li > a
Purchase div.footNav_shell > ul > li > a
Licensing div.footNav_shell > ul > li > a
Tools & Utilities div.footNav_shell > ul > li > a
Beta Releases div.footNav_shell > ul > li > a
Support Overview div.footNav_shell > ul > li > a
Knowledge Base div.footNav_shell > ul > li > a
Documentation div.footNav_shell > ul > li > a
Discussion Forum div.footNav_shell > ul > li > a
Raise Support Ticket div.footNav_shell > ul > li > a
System Requirements div.footNav_shell > ul > li > a
Online Diagnostic Utilities div.footNav_shell > ul > li > a
General div.footNav_shell > ul > li > a
Resources div.footNav_shell > ul > li > a
Resellers div.footNav_shell > ul > li > a
Services div.footNav_shell > ul > li > a
Hosting div.footNav_shell > ul > li > a
Control Panel div.footNav_shell > ul > li > a
Integration div.footNav_shell > ul > li > a
Announcements div.footNav_shell > ul > li > a
Contact Us div.footNav_shell > ul > li > a
Technical Support div.footNav_shell > ul > li > a
Raise Suggestion div.footNav_shell > ul > li > a
Media Downloads div.footNav_shell > ul > li > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●Document has a `<title>` element
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○`[role]`s have all required `[aria-*]` attributes
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○`[role]` values are valid
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has a valid value for its `[lang]` attribute
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Image elements have `[alt]` attributes
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
81

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
AttributionReporting
connect.facebook.net/en_US/fbevents.js line 279, col 769
●Uses HTTPS
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No browser errors logged to the console
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
92

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
mailenable.com/standard_edition.aspMore info
mailenable.com/professional-edition.aspMore info
mailenable.com/enterprise-edition.aspMore info
mailenable.com/premium-edition.aspMore info

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

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links are crawlable
●robots.txt is valid
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○Image elements have `[alt]` attributes

Send Feedback