Hhana.biz Site Title

北海道そのへんの花

Hhana.biz Meta Description

北海道でそのへんに咲いている花を紹介しています

Hhana.biz Test Results

Hhana.biz Mobile Performance: 86/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Serve images in next-gen formats
Potential savings of 23 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.
Efficiently encode images
Potential savings of 5 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Eliminate render-blocking resources
Potential savings of 40 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.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Minimize main-thread work
3.2 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
2,530 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce unused JavaScript
Potential savings of 124 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.
Enable text compression
Potential savings of 30 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Defer offscreen images
Potential savings of 3 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.
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().
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
15 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Time to Interactive
5.0 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.

Hhana.biz Mobile SEO: 92/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Hhana.biz Mobile Best Practices: 41/100
Quick overview:
Trust and Safety
Does not use HTTPS
19 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.
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
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
User Experience
Document doesn't use legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes. Text is illegible because there's no viewport meta tag optimized for mobile screens.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Browser Compatibility
Charset declaration is missing or occurs too late in the HTML
A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration. Expected publicId to be an empty string
Hhana.biz Mobile Accessibility: 95/100
Quick overview:
Tables do not use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead of cells with the `colspan]` attribute may improve the experience for screen reader users. [Learn more about captions.
`<td>` elements in a large `<table>` do not have table headers.
Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.
Best practices
These items highlight common accessibility best practices.
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Similar tests
www.hhana.com
www.hhana.net
www.hhana.org
www.hhana.info
www.hhana.biz
www.hhana.us
www.hhana.mobi
www.hana.biz
www.hhana.biz
www.bhana.biz
www.hbhana.biz
www.bhhana.biz
www.ghana.biz
www.hghana.biz
www.ghhana.biz
www.yhana.biz
www.hyhana.biz
www.yhhana.biz
www.uhana.biz
www.huhana.biz
www.uhhana.biz
www.jhana.biz
www.hjhana.biz
www.jhhana.biz
www.nhana.biz
www.hnhana.biz
www.nhhana.biz
www.hbana.biz
www.hhbana.biz
www.hgana.biz
www.hhgana.biz
www.hyana.biz
www.hhyana.biz
www.huana.biz
www.hhuana.biz
www.hjana.biz
www.hhjana.biz
www.hnana.biz
www.hhnana.biz
www.hhna.biz
www.hhqna.biz
www.hhaqna.biz
www.hhqana.biz
www.hhwna.biz
www.hhawna.biz
www.hhwana.biz
www.hhsna.biz
www.hhasna.biz
www.hhsana.biz
www.hhzna.biz
www.hhazna.biz
www.hhzana.biz
www.hhaa.biz
www.hhaba.biz
www.hhanba.biz
www.hhabna.biz
www.hhaha.biz
www.hhanha.biz
www.hhahna.biz
www.hhaja.biz
www.hhanja.biz
www.hhajna.biz
www.hhama.biz
www.hhanma.biz
www.hhamna.biz
www.hhan.biz
www.hhanq.biz
www.hhanaq.biz
www.hhanqa.biz
www.hhanw.biz
www.hhanaw.biz
www.hhanwa.biz
www.hhans.biz
www.hhanas.biz
www.hhansa.biz
www.hhanz.biz
www.hhanaz.biz
www.hhanza.biz
Last Tested: