Retype.com Test Results

Retype.com Desktop Performance: 92/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid multiple page redirects
Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Avoid an excessive DOM size
1,008 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Reduce unused JavaScript
Potential savings of 73 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.
Properly size images
Potential savings of 40 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Serve images in next-gen formats
Potential savings of 28 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
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 about adopting passive event listeners.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Max Potential First Input Delay
270 ms
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.

Retype.com Desktop SEO: 85/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Retype.com Desktop Best Practices: 82/100
Quick overview:
Trust and Safety
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 served over 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 about HTTPS.
Retype.com Desktop Accessibility: 66/100
Quick overview:
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.
Links do not have a discernible name
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.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
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 how to make buttons more accessible.
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.
`button`, `link`, and `menuitem` elements do not have accessible names.
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Contrast
These are opportunities to improve the legibility of your content.
Links rely on color to be distinguishable.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Similar sites
Similar tests
www.retype.com
www.retype.net
www.retype.org
www.retype.info
www.retype.biz
www.retype.us
www.retype.mobi
www.etype.com
www.retype.com
www.eetype.com
www.reetype.com
www.eretype.com
www.detype.com
www.rdetype.com
www.dretype.com
www.fetype.com
www.rfetype.com
www.fretype.com
www.tetype.com
www.rtetype.com
www.tretype.com
www.rtype.com
www.rwtype.com
www.rewtype.com
www.rwetype.com
www.rstype.com
www.restype.com
www.rsetype.com
www.rdtype.com
www.redtype.com
www.rrtype.com
www.rertype.com
www.rretype.com
www.reype.com
www.rerype.com
www.retrype.com
www.refype.com
www.retfype.com
www.reftype.com
www.regype.com
www.retgype.com
www.regtype.com
www.reyype.com
www.retyype.com
www.reytype.com
www.retpe.com
www.rettpe.com
www.retytpe.com
www.rettype.com
www.retgpe.com
www.retygpe.com
www.rethpe.com
www.retyhpe.com
www.rethype.com
www.retupe.com
www.retyupe.com
www.retuype.com
www.retye.com
www.retyoe.com
www.retypoe.com
www.retyope.com
www.retyle.com
www.retyple.com
www.retylpe.com
www.retyp.com
www.retypw.com
www.retypew.com
www.retypwe.com
www.retyps.com
www.retypes.com
www.retypse.com
www.retypd.com
www.retyped.com
www.retypde.com
www.retypr.com
www.retyper.com
www.retypre.com
www.retype.con
Last Tested: