Locondo.jp Site Title

靴&ファッション通販 ロコンド〜自宅で試着、気軽に返品

Locondo.jp Meta Description

約2000ブランドを公式取扱中の靴&ファッション通販。即日出荷・サイズ交換無料・返品無料。パンプスもブーツもサンダルもフラットシューズもスニーカーもビジネスもバッグもアパレルもアクセサリーも時計も全て自宅で楽ちん試着!

Locondo.jp Test Results

Locondo.jp Desktop Performance: 45/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Properly size images. Potential savings of 1,536 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Defer offscreen images. Potential savings of 1,447 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 512 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.
Avoid multiple page redirects. Potential savings of 380 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Eliminate render-blocking resources. Potential savings of 300 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Use video formats for animated content. Potential savings of 80 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more
Reduce initial server response time. Root document took 620 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Remove unused JavaScript. 0 ms
Remove unused JavaScript to reduce bytes consumed by network activity. 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.
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
242 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoid an excessive DOM size
3,607 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Avoid enormous network payloads
Total size was 4,742 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Minimize main-thread work
2.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Keep request counts low and transfer sizes small
347 requests • 4,742 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid long main-thread tasks
8 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
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Avoid chaining critical requests
47 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.

Locondo.jp Desktop SEO: 64/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.
Document does not have a valid `rel=canonical`
Canonical links suggest which URL to show in search results. Learn more. Points to the domain's root URL (the homepage), instead of an equivalent page of content
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 More
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more. No `<meta name="viewport">` tag found

Locondo.jp Desktop Best Practices: 62/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
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more. Expected publicId to be an empty string
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
11 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
2 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.
Locondo.jp Desktop Progressive Web App: 11/100
Quick overview:
PWA Optimized
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
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.
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
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more. No `<meta name="viewport">` tag found
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.
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
2 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
`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.
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 27.9 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.
Locondo.jp Desktop Accessibility: 69/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.
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 more.
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 more.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
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.
Tables and lists
These are opportunities to to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
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.
`<dl>`'s do not contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn more.
List items (`<li>`) are not contained within `<ul>` or `<ol>` parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn more.
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.
Similar tests
www.locondo.com
www.locondo.net
www.locondo.org
www.locondo.info
www.locondo.biz
www.locondo.us
www.locondo.mobi
www.ocondo.jp
www.locondo.jp
www.pocondo.jp
www.lpocondo.jp
www.plocondo.jp
www.oocondo.jp
www.loocondo.jp
www.olocondo.jp
www.kocondo.jp
www.lkocondo.jp
www.klocondo.jp
www.lcondo.jp
www.licondo.jp
www.loicondo.jp
www.liocondo.jp
www.lkcondo.jp
www.lokcondo.jp
www.llcondo.jp
www.lolcondo.jp
www.llocondo.jp
www.lpcondo.jp
www.lopcondo.jp
www.loondo.jp
www.loxondo.jp
www.locxondo.jp
www.loxcondo.jp
www.lodondo.jp
www.locdondo.jp
www.lodcondo.jp
www.lofondo.jp
www.locfondo.jp
www.lofcondo.jp
www.lovondo.jp
www.locvondo.jp
www.lovcondo.jp
www.locndo.jp
www.locindo.jp
www.locoindo.jp
www.lociondo.jp
www.lockndo.jp
www.locokndo.jp
www.lockondo.jp
www.loclndo.jp
www.locolndo.jp
www.loclondo.jp
www.locpndo.jp
www.locopndo.jp
www.locpondo.jp
www.locodo.jp
www.locobdo.jp
www.loconbdo.jp
www.locobndo.jp
www.locohdo.jp
www.loconhdo.jp
www.locohndo.jp
www.locojdo.jp
www.loconjdo.jp
www.locojndo.jp
www.locomdo.jp
www.loconmdo.jp
www.locomndo.jp
www.locono.jp
www.loconxo.jp
www.locondxo.jp
www.loconxdo.jp
www.loconso.jp
www.locondso.jp
www.loconsdo.jp
www.loconeo.jp
www.locondeo.jp
www.loconedo.jp
www.loconro.jp
www.locondro.jp
www.loconrdo.jp
www.loconfo.jp
www.locondfo.jp
www.loconfdo.jp
www.loconco.jp
www.locondco.jp
www.loconcdo.jp
www.locond.jp
www.locondi.jp
www.locondoi.jp
www.locondio.jp
www.locondk.jp
www.locondok.jp
www.locondko.jp
www.locondl.jp
www.locondol.jp
www.locondlo.jp
www.locondp.jp
www.locondop.jp
www.locondpo.jp
Last Tested:

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