skillshare.com - Online Classes by Skillshare | Start for Free Today (2024)

Remove unused JavaScript. Potential savings of 419KiB

Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.

Eliminate render-blocking resources. Potential savings of 510ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

Remove unused CSS. Potential savings of 37KiB

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Reduce the impact of third-party code

Third-party code blocked the main thread for 1,040ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Does not use passive listeners to improve scrolling performance

Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.

Ensure text remains visible during webfont load

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Minimize main-thread work

11.8s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more

Reduce JavaScript execution time

8.5s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Avoid an excessive DOM size

1,930 elements

Serve static assets with an efficient cache policy

22 resources found

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

Avoid long main-thread tasks

20 long tasks found

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more

Keep request counts low and transfer sizes small

94 requests • 2,013 KiB

To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

User Timing marks and measures

5 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Avoid chaining critical requests

9 chains found

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Largest Contentful Paint element

1 element found

This is the largest contentful element painted within the viewport. Learn More

Tap targets are not sized appropriately

99% appropriately sized tap targets

Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.

Includes front-end JavaScript libraries with known security vulnerabilities

1 vulnerability detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.

Does not use HTTPS

1 insecure request found

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.

Browser errors were logged to the console

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more

Page lacks the HTML doctype, thus triggering quirks-mode

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more. Expected publicId to be an empty string

Does not set a theme color for the address bar.

The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched,No `<meta name="theme-color">` tag found.

Manifest doesn't have a maskable icon

A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched

Is not configured for a custom splash screen

A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.

`start_url` does not respond with a 200 when offline

A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.

Current page does not respond with a 200 when offline

If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.

Page load is not fast enough on mobile networks

Interactive at 15.5s

A fast page load over a cellular network ensures a good mobile user experience. Learn more. Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the "Performance" section to learn how to improve.

Web app manifest does not meet the installability requirements

Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.

Does not register a service worker that controls page and `start_url`

The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.

Does not use HTTPS

1 insecure request found

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.

Buttons do not have an accessible name

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