Gujozome.jp Site Title

郡上本染 渡辺染物店 | 手描き本染鯉のぼり・藍染・藍染体験 | 岐阜県郡上八幡

Gujozome.jp Meta Description

山懐に深く抱かれた城下町、郡上八幡に創業して四百三十年、藍染一筋にその伝統の工芸技術を継承し、昭和五十二年「岐阜県重要無形文化財」に指定されました。藍染は、草で青・紺色などに染めるもので、布を何回か浸して染めあげる江戸時代からの染色方法です。

Gujozome.jp Test Results

Gujozome.jp Mobile Performance: 9/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Defer offscreen images. Potential savings of 3,165 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Serve images in next-gen formats. Potential savings of 1,486 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Properly size images. Potential savings of 1,223 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Efficiently encode images. Potential savings of 415 KiB
Optimized images load faster and consume less cellular data. Learn more.
Reduce initial server response time. Root document took 970 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Remove unused JavaScript. Potential savings of 41 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Enable text compression. Potential savings of 92 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. 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.
Reduce the impact of third-party code
Third-party code blocked the main thread for 1,880 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 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.
Serve static assets with an efficient cache policy
65 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoid enormous network payloads
Total size was 8,089 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Minimize main-thread work
10.5 s
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
3.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoids an excessive DOM size
767 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. 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
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Keep request counts low and transfer sizes small
83 requests • 8,089 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid large layout shifts
4 elements found
These DOM elements contribute most to the CLS of the page.
Avoid chaining critical requests
12 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.

Gujozome.jp Mobile SEO: 100/100
Quick overview:

Gujozome.jp Mobile Best Practices: 64/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
Trust and Safety
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Does not use HTTPS
64 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 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.
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
Gujozome.jp Mobile Progressive Web App: 18/100
Quick overview:
Installable
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.
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 use HTTPS
64 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 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.
Fast and reliable
Page load is not fast enough on mobile networks
Interactive at 13.7 s
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.
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.
`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.
PWA Optimized
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.
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.
Does not redirect HTTP traffic to HTTPS
If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Gujozome.jp Mobile Accessibility: 77/100
Quick overview:
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 more.
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.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
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.
Similar tests
www.gujozome.com
www.gujozome.net
www.gujozome.org
www.gujozome.info
www.gujozome.biz
www.gujozome.us
www.gujozome.mobi
www.ujozome.jp
www.gujozome.jp
www.fujozome.jp
www.gfujozome.jp
www.fgujozome.jp
www.vujozome.jp
www.gvujozome.jp
www.vgujozome.jp
www.tujozome.jp
www.gtujozome.jp
www.tgujozome.jp
www.bujozome.jp
www.gbujozome.jp
www.bgujozome.jp
www.yujozome.jp
www.gyujozome.jp
www.ygujozome.jp
www.hujozome.jp
www.ghujozome.jp
www.hgujozome.jp
www.gjozome.jp
www.gyjozome.jp
www.guyjozome.jp
www.ghjozome.jp
www.guhjozome.jp
www.gjjozome.jp
www.gujjozome.jp
www.gjujozome.jp
www.gijozome.jp
www.guijozome.jp
www.giujozome.jp
www.guozome.jp
www.gunozome.jp
www.gujnozome.jp
www.gunjozome.jp
www.guhozome.jp
www.gujhozome.jp
www.guuozome.jp
www.gujuozome.jp
www.guujozome.jp
www.guiozome.jp
www.gujiozome.jp
www.gukozome.jp
www.gujkozome.jp
www.gukjozome.jp
www.gumozome.jp
www.gujmozome.jp
www.gumjozome.jp
www.gujzome.jp
www.gujizome.jp
www.gujoizome.jp
www.gujkzome.jp
www.gujokzome.jp
www.gujlzome.jp
www.gujolzome.jp
www.gujlozome.jp
www.gujpzome.jp
www.gujopzome.jp
www.gujpozome.jp
www.gujoome.jp
www.gujoxome.jp
www.gujozxome.jp
www.gujoxzome.jp
www.gujosome.jp
www.gujozsome.jp
www.gujoszome.jp
www.gujoaome.jp
www.gujozaome.jp
www.gujoazome.jp
www.gujozme.jp
www.gujozime.jp
www.gujozoime.jp
www.gujoziome.jp
www.gujozkme.jp
www.gujozokme.jp
www.gujozkome.jp
www.gujozlme.jp
www.gujozolme.jp
www.gujozlome.jp
www.gujozpme.jp
www.gujozopme.jp
www.gujozpome.jp
www.gujozoe.jp
www.gujozone.jp
www.gujozomne.jp
www.gujozonme.jp
www.gujozoje.jp
www.gujozomje.jp
www.gujozojme.jp
www.gujozoke.jp
www.gujozomke.jp
www.gujozom.jp
www.gujozomw.jp
www.gujozomew.jp
www.gujozomwe.jp
www.gujozoms.jp
www.gujozomes.jp
www.gujozomse.jp
www.gujozomd.jp
www.gujozomed.jp
www.gujozomde.jp
www.gujozomr.jp
www.gujozomer.jp
www.gujozomre.jp
Last Tested:

This website uses cookies to ensure you get the best experience on our website. Learn more. Got it.