Exaw.co.kr Site Title
exaw.co.kr
Exaw.co.kr Meta Description
exaw.co.kr
Exaw.co.kr Test Results
Exaw.co.kr Mobile Performance: 76/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
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
Efficiently encode images
Potential savings of 262 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Eliminate render-blocking resources
Potential savings of 1,260 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.
Largest Contentful Paint element
3,900 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Serve images in next-gen formats
Potential savings of 962 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.
Minify JavaScript
Potential savings of 10 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Defer offscreen images
Potential savings of 277 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.
Enable text compression
Potential savings of 47 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Avoid large layout shifts
4 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
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.
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().
Serve static assets with an efficient cache policy
39 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
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
Max Potential First Input Delay
180 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.
First Meaningful Paint
2.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Exaw.co.kr Mobile SEO: 75/100
Quick overview:
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
robots.txt is not valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt. Lighthouse was unable to download a robots.txt file
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 about the `alt` attribute.
Exaw.co.kr Mobile Best Practices: 66/100
Quick overview:
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. No `<meta name="viewport">` tag found
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.
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.
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
45 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.
Browser Compatibility
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. Document must contain a doctype
Exaw.co.kr Mobile Accessibility: 66/100
Quick overview:
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
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.
`button`, `link`, and `menuitem` elements do not have accessible names.
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
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.
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 about the `alt` attribute.
Similar sites
Similar tests
www.exaw.com
www.exaw.net
www.exaw.org
www.exaw.info
www.exaw.biz
www.exaw.us
www.exaw.mobi
www.xaw.co.kr
www.exaw.co.kr
www.wxaw.co.kr
www.ewxaw.co.kr
www.wexaw.co.kr
www.sxaw.co.kr
www.esxaw.co.kr
www.dxaw.co.kr
www.edxaw.co.kr
www.dexaw.co.kr
www.rxaw.co.kr
www.erxaw.co.kr
www.rexaw.co.kr
www.eaw.co.kr
www.ezaw.co.kr
www.exzaw.co.kr
www.ezxaw.co.kr
www.esaw.co.kr
www.exsaw.co.kr
www.edaw.co.kr
www.exdaw.co.kr
www.ecaw.co.kr
www.excaw.co.kr
www.ecxaw.co.kr
www.exw.co.kr
www.exqw.co.kr
www.exaqw.co.kr
www.exqaw.co.kr
www.exww.co.kr
www.exaww.co.kr
www.exwaw.co.kr
www.exsw.co.kr
www.exasw.co.kr
www.exzw.co.kr
www.exazw.co.kr
www.exa.co.kr
www.exaq.co.kr
www.exawq.co.kr
www.exaa.co.kr
www.exawa.co.kr
www.exaaw.co.kr
www.exas.co.kr
www.exaws.co.kr
www.exae.co.kr
www.exawe.co.kr
www.exaew.co.kr
www.exaw.net
www.exaw.org
www.exaw.info
www.exaw.biz
www.exaw.us
www.exaw.mobi
www.xaw.co.kr
www.exaw.co.kr
www.wxaw.co.kr
www.ewxaw.co.kr
www.wexaw.co.kr
www.sxaw.co.kr
www.esxaw.co.kr
www.dxaw.co.kr
www.edxaw.co.kr
www.dexaw.co.kr
www.rxaw.co.kr
www.erxaw.co.kr
www.rexaw.co.kr
www.eaw.co.kr
www.ezaw.co.kr
www.exzaw.co.kr
www.ezxaw.co.kr
www.esaw.co.kr
www.exsaw.co.kr
www.edaw.co.kr
www.exdaw.co.kr
www.ecaw.co.kr
www.excaw.co.kr
www.ecxaw.co.kr
www.exw.co.kr
www.exqw.co.kr
www.exaqw.co.kr
www.exqaw.co.kr
www.exww.co.kr
www.exaww.co.kr
www.exwaw.co.kr
www.exsw.co.kr
www.exasw.co.kr
www.exzw.co.kr
www.exazw.co.kr
www.exa.co.kr
www.exaq.co.kr
www.exawq.co.kr
www.exaa.co.kr
www.exawa.co.kr
www.exaaw.co.kr
www.exas.co.kr
www.exaws.co.kr
www.exae.co.kr
www.exawe.co.kr
www.exaew.co.kr