Skip to content
https://teachable.com

Lighthouse Mobile

· 0 checks — Mobile 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.

36

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.

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.

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:73.304 source:map[column:34521 line:9 type:source-location url:https://cdn.prod.website-files.com/gsap/3.15.0/ScrollTrigger.min.js urlProvider:network]] map[reflowTime:0.443 source:map[column:13814 line:9 type:source-location url:https://cdn.prod.website-files.com/gsap/3.15.0/ScrollTrigger.min.js urlProvider:network]] map[reflowTime:0.152 source:map[column:12978 line:9 type:source-location url:https://cdn.prod.website-files.com/gsap/3.15.0/ScrollTrigger.min.js urlProvider:network]] map[reflowTime:0.383 source:map[column:17230 line:9 type:source-location url:https://cdn.prod.website-files.com/gsap/3.15.0/ScrollTrigger.min.js urlProvider:network]] map[reflowTime:2.071 source:map[column:4560 line:12 type:source-location url:https://cdn.jsdelivr.net/npm/swiper@12/swiper-bundle.min.js urlProvider:network]] map[reflowTime:1.601 source:map[column:10280 line:12 type:source-location url:https://cdn.jsdelivr.net/npm/swiper@12/swiper-bundle.min.js urlProvider:network]] map[reflowTime:1.148 source:map[column:16795 line:12 type:source-location url:https://cdn.jsdelivr.net/npm/swiper@12/swiper-bundle.min.js urlProvider:network]] map[reflowTime:0.259 source:map[column:10760 line:12 type:source-location url:https://cdn.jsdelivr.net/npm/swiper@12/swiper-bundle.min.js urlProvider:network]] map[reflowTime:1.407 source:map[column:254661 line:3 type:source-location url:https://cdn.intellimize.co/snippet/117475503.js urlProvider:network]] map[reflowTime:20.687 source:map[column:232 line:0 type:source-location url:https://cdn.prod.website-files.com/687904fb2b26c434698c47e9/js/fs-teachable.achunk.496d56dd8c063ec0.js urlProvider:network]]]

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

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.

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
a.teach_content > div.teach_frame > div.teach_frame-img-wrp > img.teach_frame-img a.teach_content > div.teach_frame > div.teach_frame-img-wrp > img.teach_frame-img
/687904fb2b26c434698c47e9/68e2fc0c780c5ef76265386b_2d5918...144.4 KiB126.6 KiB
a.teach_content > div.teach_frame > div.teach_frame-img-wrp > img.teach_frame-img a.teach_content > div.teach_frame > div.teach_frame-img-wrp > img.teach_frame-img
/687904fb2b26c434698c47e9/68e2fc0c548905717e540783_3ce187...81.4 KiB63.7 KiB
a.teach_content > div.teach_frame > div.teach_frame-img-wrp > img.teach_frame-img a.teach_content > div.teach_frame > div.teach_frame-img-wrp > img.teach_frame-img
/687904fb2b26c434698c47e9/68e2fc0c8ae5b217815396ad_272dd0...61.6 KiB43.9 KiB
section.section_why > div.why_bg-color-wrp > div.why_bg-img-wrp > img.why_bg-img section.section_why > div.why_bg-color-wrp > div.why_bg-img-wrp > img.why_bg-img
/687904fb2b26c434698c47e9/68beb37e8514967a4d013c17_temp-s...41.3 KiB23.0 KiB
a.teach_content > div.teach_frame > div.teach_frame-img-wrp > img.teach_frame-img a.teach_content > div.teach_frame > div.teach_frame-img-wrp > img.teach_frame-img
/687904fb2b26c434698c47e9/68e2fc0c583104a037c344a8_676e42...35.3 KiB17.5 KiB

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 933 ms
URLTime Spent
teachable.com/933 ms
www.teachable.com/0.0 ms

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

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 170 ms 14.6 KiB
URLTransfer SizeEst Savings
/687904fb2b26c434698c47e9/css/fs-teachable.68b18a352897a2...28.1 KiB14.6 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.

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTotal CPU TimeScript EvaluationScript Parse
cdn.prod.website-files.com/gsap/3.15.0/gsap.min.js554 ms145 ms6.4 ms
Unattributable401 ms17 ms0.0 ms
www.googletagmanager.com/gtm.js?id=GTM-KJQCH7P381 ms324 ms45 ms
cdn.prod.website-files.com/gsap/3.15.0/ScrollTrigger.min.js351 ms42 ms4.7 ms
www.googletagmanager.com/gtag/js?id=AW-959285871&cx=c&gtm=4e64h1350 ms310 ms36 ms
www.teachable.com/336 ms148 ms20 ms
/pages/versioned/common-scripts/4ce8c7df8d425cc5046457682...302 ms269 ms14 ms
www.googletagmanager.com/gtag/js?id=G-6E9Q4KD1X0&cx=c&gtm=4e64h1202 ms157 ms44 ms
cdn.jsdelivr.net/npm/swiper@12/swiper-bundle.min.js178 ms66 ms17 ms
/687904fb2b26c434698c47e9/js/fs-teachable.achunk.55097dd6...174 ms152 ms14 ms
cdn.flowblock.co/public/files/68e91c7073e805ab57462f0c/gsap.js169 ms81 ms11 ms
cdn.heapanalytics.com/js/heap-318805607.js146 ms128 ms10 ms
cdn.intellimize.co/snippet/117475503.js136 ms89 ms41 ms
cdn.flowblock.co/public/files/687904fb2b26c434698c47e9/case-study-slider.js117 ms27 ms0.6 ms
/scripts/addons/thirdparty/c00d2378dcf12c80724efc85b3c849...115 ms67 ms48 ms
cdn.flowblock.co/public/files/687904fb2b26c434698c47e9/stories-slider.js99 ms73 ms0.6 ms
/687904fb2b26c434698c47e9/js/fs-teachable.achunk.abb66f7f...96 ms79 ms3.3 ms
/687904fb2b26c434698c47e9/js/fs-teachable.achunk.496d56dd...86 ms2.2 ms0.5 ms
script.crazyegg.com/scripts/addons/1.0.146/survey.js80 ms57 ms23 ms
/pages/versioned/tracking-scripts/158692313dc4b9f2e28d9e9...72 ms62 ms9.0 ms
static.auth.hotmart.com/cookie-policy/teachable.js?lang=en69 ms57 ms9.6 ms
/js/jquery-3.5.1.min.dc5e7f18c8.js?site=687904fb2b26c4346...60 ms38 ms12 ms
/687904fb2b26c434698c47e9/js/fs-teachable.achunk.bec7a721...60 ms53 ms6.2 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation2.6 s
Style & Layout811 ms
Other735 ms
Script Parsing & Compilation403 ms
Rendering100 ms
Parse HTML & CSS77 ms
Garbage Collection46 ms

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 2.3 KiB
URLTransfer SizeEst Savings
:host { --loader-background: var(--color-grey-20); … } …3.3 KiB2.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
●LCP request discovery
●Modern HTTP
●Optimize viewport for mobile
●Minify JavaScript
●Avoids enormous network payloads Total size was 2,089 KiB
●User Timing marks and measures 7 user timings
●Avoid long main-thread tasks 20 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 100 ms
●Server Backend Latencies 180 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 60 ms
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
85

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Abagail Pumphrey BOSS PROJECT Read case study Brian Kouhi TOANIMATE Read case s… div.case-study_content-r > div.cs-slider_instance > div.cs-slider_list-wrapper > div#swiper-wrapper-d16c76219d6fdfe7

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.stories_wrp > div.stories-slider_instance > div.stories-slider_navigation > button.stories-slider_previous div.stories_wrp > div.stories-slider_instance > div.stories-slider_navigation > button.stories-slider_previous
div.stories_wrp > div.stories-slider_instance > div.stories-slider_navigation > button.stories-slider_next div.stories_wrp > div.stories-slider_instance > div.stories-slider_navigation > button.stories-slider_next
div.case-study_content-r > div.cs-slider_instance > div.cs-slider_navigation > button.cs-slider_button div.case-study_content-r > div.cs-slider_instance > div.cs-slider_navigation > button.cs-slider_button
div.case-study_content-r > div.cs-slider_instance > div.cs-slider_navigation > button.cs-slider_button div.case-study_content-r > div.cs-slider_instance > div.cs-slider_navigation > button.cs-slider_button

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
nav.nav_component > div.nav_wrapper > div.nav_content-l > a.nav_brand-link nav.nav_component > div.nav_wrapper > div.nav_content-l > a.nav_brand-link
div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link
div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link
div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link
div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link
div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link
div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link
div.footer_wrp > div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > a.footer_soc2-badge-2-2 div.footer_wrp > div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > a.footer_soc2-badge-2-2
div.padding-global > div.footer_wrp > div.footer_grid > a#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0de5-3c6d0d7e div.padding-global > div.footer_wrp > div.footer_grid > a#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0de5-3c6d0d7e

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.

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
Explore div.footer_wrp > div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0d82-3c6d0d7e > h4.footer_title-text

These are opportunities to improve keyboard navigation in your application.

○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-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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 an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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.
96

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
[OptinMonster] This account is not currently active. It is either expired, paused, archived, cancelled or temporarily suspended.
Failed to load resource: the server responded with a status of 401 ()
www.teachable.com/ line 939, col 23
TypeError: Cannot set properties of null (setting 'textContent') at HTMLDocument.<anonymous> (https://www.teachable.com/:940:24)
●Uses HTTPS
●Avoids deprecated APIs
●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 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
100

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.

○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 have descriptive text
●Links are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback