Kefei.com Test Results

Kefei.com Mobile Performance: 58/100
Quick overview:
Max Potential First Input Delay
400 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.
Time to Interactive
7.6 s
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.
First Meaningful Paint
3.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce JavaScript execution time
1.8 s
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.
Reduce the impact of third-party code
Third-party code blocked the main thread for 1,090 ms
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 how to minimize third-party impact.
Properly size images
Potential savings of 47 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 324 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.
Eliminate render-blocking resources
Potential savings of 1,950 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Reduce unused CSS
Potential savings of 29 KiB
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.
Minimize main-thread work
4.5 s
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
Largest Contentful Paint element
5,270 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
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
Serve static assets with an efficient cache policy
31 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Reduce unused JavaScript
Potential savings of 50 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.
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.
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn how to avoid document.write().
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 about `font-display`.
Minify CSS
Potential savings of 4 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Kefei.com Mobile SEO: 82/100
Quick overview:
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.
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

Kefei.com Mobile Best Practices: 79/100
Quick overview:
Trust and Safety
Does not use HTTPS
28 insecure requests 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.
Does not redirect HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Kefei.com Mobile Accessibility: 57/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.
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.
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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
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.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Similar tests
www.kefei.com
www.kefei.net
www.kefei.org
www.kefei.info
www.kefei.biz
www.kefei.us
www.kefei.mobi
www.efei.com
www.kefei.com
www.jefei.com
www.kjefei.com
www.jkefei.com
www.iefei.com
www.kiefei.com
www.ikefei.com
www.mefei.com
www.kmefei.com
www.mkefei.com
www.lefei.com
www.klefei.com
www.lkefei.com
www.oefei.com
www.koefei.com
www.okefei.com
www.kfei.com
www.kwfei.com
www.kewfei.com
www.kwefei.com
www.ksfei.com
www.kesfei.com
www.ksefei.com
www.kdfei.com
www.kedfei.com
www.kdefei.com
www.krfei.com
www.kerfei.com
www.krefei.com
www.keei.com
www.kecei.com
www.kefcei.com
www.kecfei.com
www.kedei.com
www.kefdei.com
www.kerei.com
www.kefrei.com
www.ketei.com
www.keftei.com
www.ketfei.com
www.kegei.com
www.kefgei.com
www.kegfei.com
www.kevei.com
www.kefvei.com
www.kevfei.com
www.kefi.com
www.kefwi.com
www.kefewi.com
www.kefwei.com
www.kefsi.com
www.kefesi.com
www.kefsei.com
www.kefdi.com
www.kefedi.com
www.kefri.com
www.keferi.com
www.kefe.com
www.kefeu.com
www.kefeiu.com
www.kefeui.com
www.kefej.com
www.kefeij.com
www.kefeji.com
www.kefek.com
www.kefeik.com
www.kefeki.com
www.kefeo.com
www.kefeio.com
www.kefeoi.com
www.kefei.con
Last Tested: