Body360.co.kr Site Title

바디360

Body360.co.kr Meta Description

나를 위한 일상 속 리프레시, 360+

Body360.co.kr Test Results

Body360.co.kr Mobile Performance: 57/100
Quick overview:
Network dependency tree
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Document request latency
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Forced reflow
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about forced reflow and its mitigations.
Render blocking requests
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Use efficient cache lifetimes
Est savings of 4,228 KiB
A long cache lifetime can speed up repeat visits to your page. Learn more.
Font display
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Time to Interactive
10.3 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.
Improve image delivery
Est savings of 316 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Modern HTTP
HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Serve images in next-gen formats
Est savings of 1,194 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.
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.
Reduce unused JavaScript
Est savings of 130 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.
Largest Contentful Paint element
10,120 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Minify JavaScript
Est savings of 37 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Eliminate render-blocking resources
Est savings of 2,130 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.
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
19 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid enormous network payloads
Total size was 5,060 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Avoid serving legacy JavaScript to modern browsers
Est savings of 6 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support legacy browsers. Learn why most sites can deploy ES6+ code without transpiling
Enable text compression
Est savings of 8 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Minify CSS
Est savings of 2 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
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`.
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.

Body360.co.kr Mobile SEO: 83/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
3 links found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
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

Body360.co.kr Mobile Best Practices: 69/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 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.
Does not use HTTPS
22 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.
User Experience
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.
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.
Body360.co.kr Mobile Accessibility: 83/100
Quick overview:
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Elements use prohibited ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
`[aria-*]` attributes are not valid or misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
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.
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.
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.
Similar tests
www.body360.com
www.body360.net
www.body360.org
www.body360.info
www.body360.biz
www.body360.us
www.body360.mobi
www.ody360.co.kr
www.body360.co.kr
www.vody360.co.kr
www.bvody360.co.kr
www.vbody360.co.kr
www.gody360.co.kr
www.bgody360.co.kr
www.gbody360.co.kr
www.hody360.co.kr
www.bhody360.co.kr
www.hbody360.co.kr
www.nody360.co.kr
www.bnody360.co.kr
www.nbody360.co.kr
www.bdy360.co.kr
www.bidy360.co.kr
www.boidy360.co.kr
www.biody360.co.kr
www.bkdy360.co.kr
www.bokdy360.co.kr
www.bkody360.co.kr
www.bldy360.co.kr
www.boldy360.co.kr
www.blody360.co.kr
www.bpdy360.co.kr
www.bopdy360.co.kr
www.bpody360.co.kr
www.boy360.co.kr
www.boxy360.co.kr
www.bodxy360.co.kr
www.boxdy360.co.kr
www.bosy360.co.kr
www.bodsy360.co.kr
www.bosdy360.co.kr
www.boey360.co.kr
www.bodey360.co.kr
www.boedy360.co.kr
www.bory360.co.kr
www.bodry360.co.kr
www.bordy360.co.kr
www.bofy360.co.kr
www.bodfy360.co.kr
www.bofdy360.co.kr
www.bocy360.co.kr
www.bodcy360.co.kr
www.bocdy360.co.kr
www.bod360.co.kr
www.bodt360.co.kr
www.bodyt360.co.kr
www.bodty360.co.kr
www.bodg360.co.kr
www.bodyg360.co.kr
www.bodgy360.co.kr
www.bodh360.co.kr
www.bodyh360.co.kr
www.bodhy360.co.kr
www.bodu360.co.kr
www.bodyu360.co.kr
www.boduy360.co.kr
www.body60.co.kr
www.body30.co.kr
www.body36.co.kr
Last Tested: