페이지 보고서Deal_View
본 페이지의 내용은 2018-12-01 10:30:10 에 Chrome 브라우저 버전 기준, native 수준으로 속도를 제한한 desktop 환경에서 총 5 회의 검사를 실시한 결과입니다.
Errors
| 측정 항목 | 값 |
|---|
소요시간 요약
최소, 중간, 최대항목의 값을 클릭하여 해당 값이 나온 검사 결과 페이지로 이동할 수 있습니다.
| 항목 | 최소 | 중간 | 평균 | 최대 |
|---|
실행 동영상 확인
측정 시스템의 블랙박스 영상을 통해 측정값을 확인하실 수 있습니다.
Download videoMissing data from Browsertime.
Lighthouse (version 3.2.1)
Score
| Performance | Progressive Web App | Best Practices | Accessibility | SEO |
|---|---|---|---|---|
| 5 | 35 | 67 | 76 | 91 |
Room for improvement
Warning: All links in the description will lead you to developers.google.com
| Title | Value | Score |
|---|---|---|
| Does not register a service worker | 0 | |
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. | ||
| Does not respond with a 200 when offline | 0 | |
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more. | ||
| First Contentful Paint | 8.8 s | 3 |
First Contentful Paint marks the time at which the first text or image is painted. Learn more. | ||
| First Meaningful Paint | 8.8 s | 3 |
First Meaningful Paint measures when the primary content of a page is visible. Learn more. | ||
| Page load is not fast enough on 3G | Interactive at %d s,21.78839399999999 | 0 |
A fast page load over a 3G 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. | ||
| Speed Index | 20.5 s | 0 |
Speed Index shows how quickly the contents of a page are visibly populated. Learn more. | ||
| First CPU Idle | 8.8 s | 26 |
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more. | ||
| Time to Interactive | 21.8 s | 2 |
Interactive marks the time at which the page is fully interactive. Learn more. | ||
| User will not be prompted to Install the Web App | 0 | |
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: Manifest does not have | ||
| Is not configured for a custom splash screen | 0 | |
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: Manifest does not have a PNG icon of at least 512px,
Manifest does not have | ||
| Minimize main-thread work | 4.9 s | 35 |
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. | ||
| Reduce JavaScript execution time | 1.4 s | 87 |
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more. | ||
| Preload key requests | Potential savings of 12,180 ms | 0 |
Consider using <link rel=preload> to prioritize fetching resources that are currently requested later in page load. Learn more. | ||
| Preconnect to required origins | Potential savings of 370 ms | 71 |
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more. | ||
| Ensure text remains visible during webfont load | 0 | |
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more. | ||
| Background and foreground colors do not have a sufficient contrast ratio. | 0 | |
Low-contrast text is difficult or impossible for many users to read. Learn more. | ||
| `[id]` attributes on the page are not unique | 0 | |
The value of an id attribute must be unique to prevent other instances from being overlooked by assistive technologies. Learn more. | ||
| `[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5. | 0 | |
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. | ||
| Serve static assets with an efficient cache policy | 93 resources found | 0 |
A long cache lifetime can speed up repeat visits to your page. Learn more. | ||
| Avoid enormous network payloads | Total size was 4,883 KB | 26 |
Large network payloads cost users real money and are highly correlated with long load times. Learn more. | ||
| Defer offscreen images | Potential savings of 954 KB | 9 |
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more. | ||
| Eliminate render-blocking resources | Potential savings of 7,750 ms | 0 |
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more. | ||
| Defer unused CSS | Potential savings of 51 KB | 88 |
Remove unused rules from stylesheets to reduce unnecessary bytes consumed by network activity. Learn more. | ||
| Serve images in next-gen formats | Potential savings of 2,451 KB | 0 |
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. | ||
| Efficiently encode images | Potential savings of 1,157 KB | 0 |
Optimized images load faster and consume less cellular data. Learn more. | ||
| Properly size images | Potential savings of 2,994 KB | 0 |
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more. | ||
| Avoids an excessive DOM size | 547 nodes | 99 |
Browser engineers recommend pages contain fewer than ~1,500 DOM nodes. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more. | ||
| Links to cross-origin destinations are unsafe | 0 | |
Add | ||
| Uses `document.write()` | 0 | |
For users on slow connections, external scripts dynamically injected via | ||
| Includes front-end JavaScript libraries with known security vulnerabilities | 2 vulnerabilities detected | 0 |
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more. | ||
| Does not use HTTP/2 for all of its resources | 87 requests not served via HTTP/2 | 0 |
HTTP/2 offers many benefits over HTTP/1.1, including binary headers, multiplexing, and server push. Learn more. | ||
| Does not use passive listeners to improve scrolling performance | 0 | |
Consider marking your touch and wheel event listeners as | ||
| Document does not have a valid `rel=canonical` | 0 | |
Canonical links suggest which URL to show in search results. Learn more. Points to a root of the same origin | ||