Sorahaku.net Test Results

Sorahaku.net Mobile Performance: 44/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid an excessive DOM size
1,094 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.
Defer offscreen images
Potential savings of 903 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Minimize main-thread work
10.1 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
Eliminate render-blocking resources
Potential savings of 6,560 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 302 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.
Reduce unused JavaScript
Potential savings of 109 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 986 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Avoid multiple page redirects
Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Enable text compression
Potential savings of 421 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Largest Contentful Paint element
11,520 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Minify CSS
Potential savings of 10 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Serve images in next-gen formats
Potential savings of 1,500 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.
Reduce JavaScript execution time
1.4 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.
Avoid enormous network payloads
Total size was 22,442 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Efficiently encode images
Potential savings of 470 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Serve static assets with an efficient cache policy
53 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
First Meaningful Paint
9.7 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Max Potential First Input Delay
610 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
11.1 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.

Sorahaku.net Mobile SEO: 100/100
Quick overview:

Sorahaku.net Mobile Best Practices: 79/100
Quick overview:
General
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 about this errors in console diagnostic audit
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.
Sorahaku.net Mobile Accessibility: 88/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.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
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.
Contrast
These are opportunities to improve the legibility of your content.
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.
Elements with visible text labels do not have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Similar tests
www.sorahaku.com
www.sorahaku.net
www.sorahaku.org
www.sorahaku.info
www.sorahaku.biz
www.sorahaku.us
www.sorahaku.mobi
www.orahaku.net
www.sorahaku.net
www.worahaku.net
www.sworahaku.net
www.wsorahaku.net
www.eorahaku.net
www.seorahaku.net
www.esorahaku.net
www.dorahaku.net
www.sdorahaku.net
www.dsorahaku.net
www.zorahaku.net
www.szorahaku.net
www.zsorahaku.net
www.xorahaku.net
www.sxorahaku.net
www.xsorahaku.net
www.aorahaku.net
www.saorahaku.net
www.asorahaku.net
www.srahaku.net
www.sirahaku.net
www.soirahaku.net
www.siorahaku.net
www.skrahaku.net
www.sokrahaku.net
www.skorahaku.net
www.slrahaku.net
www.solrahaku.net
www.slorahaku.net
www.sprahaku.net
www.soprahaku.net
www.sporahaku.net
www.soahaku.net
www.soeahaku.net
www.soreahaku.net
www.soerahaku.net
www.sodahaku.net
www.sordahaku.net
www.sodrahaku.net
www.sofahaku.net
www.sorfahaku.net
www.sofrahaku.net
www.sotahaku.net
www.sortahaku.net
www.sotrahaku.net
www.sorhaku.net
www.sorqhaku.net
www.soraqhaku.net
www.sorqahaku.net
www.sorwhaku.net
www.sorawhaku.net
www.sorwahaku.net
www.sorshaku.net
www.sorashaku.net
www.sorsahaku.net
www.sorzhaku.net
www.sorazhaku.net
www.sorzahaku.net
www.soraaku.net
www.sorabaku.net
www.sorahbaku.net
www.sorabhaku.net
www.soragaku.net
www.sorahgaku.net
www.soraghaku.net
www.sorayaku.net
www.sorahyaku.net
www.sorayhaku.net
www.sorauaku.net
www.sorahuaku.net
www.sorauhaku.net
www.sorajaku.net
www.sorahjaku.net
www.sorajhaku.net
www.soranaku.net
www.sorahnaku.net
www.soranhaku.net
www.sorahku.net
www.sorahqku.net
www.sorahaqku.net
www.sorahqaku.net
www.sorahwku.net
www.sorahawku.net
www.sorahwaku.net
www.sorahsku.net
www.sorahasku.net
www.sorahsaku.net
www.sorahzku.net
www.sorahazku.net
www.sorahzaku.net
www.sorahau.net
www.sorahaju.net
www.sorahakju.net
www.sorahajku.net
www.sorahaiu.net
www.sorahakiu.net
www.sorahaiku.net
www.sorahamu.net
www.sorahakmu.net
www.sorahamku.net
www.sorahalu.net
www.sorahaklu.net
www.sorahalku.net
www.sorahaou.net
www.sorahakou.net
www.sorahaoku.net
www.sorahak.net
www.sorahaky.net
www.sorahakuy.net
www.sorahakyu.net
www.sorahakh.net
www.sorahakuh.net
www.sorahakhu.net
www.sorahakj.net
www.sorahakuj.net
www.sorahaki.net
www.sorahakui.net
Last Tested: