페이지 보고서Login
본 페이지의 내용은 2018-12-01 11:11:35 에 Chrome 브라우저 70.0.3538.67 버전 기준, native 수준으로 속도를 제한한 desktop 환경에서 총 5 회의 검사를 실시한 결과입니다.
| 측정 항목 | 값 |
|---|---|
| 퍼포먼스 점수: | 55 |
| 페이지 전체 용량: | 1.8 MB |
| 요청 횟수: | 90 |
| 첫번째 시각화 시간 [중간값]: | 1667 |
| 속도 점수 [중간값]: | 2272 |
| 시각화 85% 완료 시간 [중간값]: | 2267 |
| 시각화 95% 완료 시간 [중간값]: | 2367 |
| 시각화 99% 완료 시간 [중간값]: | 2400 |
| 마지막 시각화 (완료) [중간값]: | 2767 |
소요시간 요약
최소, 중간, 최대항목의 값을 클릭하여 해당 값이 나온 검사 결과 페이지로 이동할 수 있습니다.
| 항목 | 최소 | 중간 | 평균 | 최대 |
|---|---|---|---|---|
| SpeedIndex | 2005 | 2272 | 2228 | 2330 |
| PerceptualSpeedIndex | 1684 | 1970 | 1920 | 2040 |
| FirstVisualChange | 1367 | 1667 | 1607 | 1767 |
| LastVisualChange | 2467 | 2767 | 2720 | 2867 |
| VisualReadiness | 1066 | 1100 | 1113 | 1167 |
| VisualComplete85 | 2067 | 2267 | 2247 | 2400 |
| VisualComplete95 | 2067 | 2367 | 2327 | 2467 |
| VisualComplete99 | 2100 | 2400 | 2347 | 2500 |
| backEndTime | 123 | 142 | 139 | 152 |
| firstPaint | 769 | 1040 | 1030 | 1287 |
| fullyLoaded | 2105 | 2398 | 2358 | 2505 |
| rumSpeedIndex | 771 | 1062 | 1036 | 1288 |
Waterfall 차트
SpeedIndex 기준 5번째 검사가 중간값입니다.
실행 동영상 확인
측정 시스템의 블랙박스 영상을 통해 측정값을 확인하실 수 있습니다.
Download videoCoach
코치는 웹 서비스의 성능과 접근성 향상을 위해 웹 표준 및 성능 향상에 필요한 조치를 자동으로 검토하여 안내합니다. 더 많은 정보를 확인하려면 Lighthouse 탭 또한 참조하십시오.
검사 결과
- 총점 63
- 성능 점수 55
- 접근성 점수 96
- 최적화 점수 64
접근성 분석 결과 (96)
| 문제 | 수정 권고 | 점수 |
|---|---|---|
| Always use an alt attribute on image tags (altImages) | The page has 1 image that lack alt attribute(s) and 1 of them are unique. | 90 |
| ||
| Always set labels on inputs in forms (labelOnInput) | There are 2 input(s) that are missing labels on a form. | 80 |
| ||
성능 분석 결과 (55)
| 문제 | 수정 권고 | 점수 |
|---|---|---|
| Avoid slowing down the critical rendering path (fastRender) | The page has 34 render blocking CSS request(s) and 10 blocking JavaScript request(s) inside of head. | 0 |
| ||
| Inline CSS for faster first render (inlineCss) | The page has both inline styles as well as it is requesting 34 CSS file(s) inside of the head. Let's only inline CSS for really fast render. | 90 |
| ||
| ||
| Avoid Frontend single point of failures (spof) | The page has 2 requests inside of the head that can cause a SPOF (single point of failure). Load them asynchronously or move them outside of the document head. | 80 |
| ||
| Avoid extra requests by setting cache headers (cacheHeaders) | The page has 79 request(s) that are missing a cache time. Configure a cache time so the browser doesn't need to download them every time. It will save 1.6 MB the next access. | 0 |
| ||
| Long cache headers is good (cacheHeadersLong) | The page has 5 request(s) that have a shorter cache time than 30 days (but still a cache time). | 95 |
| ||
| Always compress text content (compressAssets) | The page has 43 request(s) that are served uncompressed. You could save a lot of bytes by sending them compressed instead. | 0 |
| ||
| Total CSS size shouldn't be too big (cssSize) | The total CSS transfer size is 725.7 kB and uncompressed size is 733.6 kB. That is big and the CSS could most probably be smaller. | 0 |
| Avoid too many fonts (fewFonts) | The page has 2 font requests. Do you really need them? What value does the fonts give the user? | 80 |
| ||
| Total JavaScript size shouldn't be too big (javascriptSize) | The total JavaScript transfer size is 756.8 kB and the uncompressed size is 1.3 MB. This is totally crazy! You need to remove as much as possible. | 0 |
| Avoid using incorrect mime types (mimeTypes) | The page has 2 misconfigured mime type(s). | 98 |
| ||
| Make each CSS response small (optimalCssSize) | https://joomoney.fund/wp-content/plugins/fiscus/assets/css/sweetalert.min.css?ver=1.0.0 size is 15.6 kB (15626) and that is bigger than the limit of 14.5 kB. https://joomoney.fund/wp-content/themes/joomoney/fonts/ionicons/ionicons.min.css?ver=2.0.0 size is 51.2 kB (51249) and that is bigger than the limit of 14.5 kB. https://joomoney.fund/wp-content/themes/joomoney/fonts/fontawesome/fontawesome.css?ver=5.0.9 size is 44.5 kB (44475) and that is bigger than the limit of 14.5 kB. https://joomoney.fund/wp-content/themes/joomoney/css/animate.css?ver=3.5.2 size is 23.8 kB (23848) and that is bigger than the limit of 14.5 kB. https://joomoney.fund/wp-content/uploads/pum/pum-site-styles.css?generated=1543577242&ver=1.7.30 size is 16.1 kB (16111) and that is bigger than the limit of 14.5 kB. https://joomoney.fund/wp-content/plugins/kboard/skin/@joom-main-slider/style.css?ver=5.3.6 size is 28.6 kB (28643) and that is bigger than the limit of 14.5 kB. https://joomoney.fund/wp-content/plugins/kboard/skin/@joom-advice/style.css?ver=5.3.6 size is 20.3 kB (20258) and that is bigger than the limit of 14.5 kB. https://joomoney.fund/wp-content/plugins/kboard/skin/@joom-news/style.css?ver=5.3.6 size is 19.1 kB (19135) and that is bigger than the limit of 14.5 kB. https://joomoney.fund/wp-content/plugins/kboard/skin/@joom-loan/style.css?ver=5.3.6 size is 29.1 kB (29116) and that is bigger than the limit of 14.5 kB. https://joomoney.fund/wp-content/themes/joomoney/style.css?ver=1.1.5.8 size is 385.8 kB (385774) and that is bigger than the limit of 14.5 kB. Try to make the CSS files fit into 14.5 KB. | 0 |
| ||
| Don't use private headers on static content (privateAssets) | The page has 3 request(s) with private headers. Make sure that the assets really should be private and only used by one user. Otherwise, make it cacheable for everyone. | 70 |
| ||
최적화 분석 결과 (64)
| 문제 | 수정 권고 | 점수 |
|---|---|---|
| Avoid using Google Analytics (ga) | The page is using Google Analytics meaning you share your users private information with Google. | 0 |
| Serve your content using HTTP/2 (httpsH2) | The page is using HTTPS but not HTTP/2. Change to HTTP/2 to follow new best practice and make the site faster. | 0 |
| Meta description (metaDescription) | The page is missing a meta description. | 0 |
페이지 정보
| 기본 정보 | |
|---|---|
| Title | 로그인 – 주머니펀드 |
| Width | 1365 |
| Height | 1501 |
| DOM elements | 346 |
| Avg DOM depth | 7 |
| Max DOM depth | 19 |
| Iframes | 0 |
| Script tags | 52 |
| Local storage | N/A |
| Session storage | N/A |
| HTML vs AMP | Plain good HTML page |
| 리소스 힌트 |
|---|
| dns-prefetch |
| https://cdnjs.cloudflare.com/ |
| https://fonts.googleapis.com/ |
| https://s.w.org/ |
| 서드파티 | |
|---|---|
| JQuery | 1.12.4 |
| Google Analytics | Yes |
| Google Tag Manager | No |
| Piwik | No |
| Boomerang | No |
| New Relic | No |
시각화 측정
| 시각화 측정 항목 | |
|---|---|
| 첫번째 시각화 | 1667 |
| 속도 점수 | 2272 |
| 지각 속도 점수 | 1970 |
| Visual Complete 85% | 2367 |
| Visual Complete 95% | 2367 |
| Visual Complete 99% | 2400 |
| 마지막 시각화 | 2767 |
Browser Metrics
| Navigation Timing | |
|---|---|
| backEndTime | 123 |
| domContentLoadedTime | 1435 |
| domInteractiveTime | 1435 |
| domainLookupTime | 1 |
| frontEndTime | 1694 |
| pageDownloadTime | 20 |
| pageLoadTime | 1837 |
| redirectionTime | 0 |
| serverConnectionTime | 40 |
| serverResponseTime | 90 |
| Specials and User Timing | |
|---|---|
| first-contentful-paint | 1287 |
| first-paint | 1287 |
| RUM Speed Index | 1288 |
| Fully loaded | 2398 |
Time spent
| Categories (ms) | |
|---|---|
| Scripting | 705.4 |
| Loading | 159.9 |
| Rendering | 570.2 |
| Painting | 7.1 |
| Events (ms) | |
|---|---|
| Layout | 465.6 |
| EvaluateScript | 433.6 |
| v8.compile | 122.2 |
| FunctionCall | 105.7 |
| ParseAuthorStyleSheet | 95.1 |
| UpdateLayoutTree | 87.3 |
| ParseHTML | 64.8 |
| MinorGC | 19.8 |
| UpdateLayerTree | 17 |
| BlinkGC.AtomicPhase | 14.8 |
| Paint | 7.1 |
| TimerFire | 6.4 |
| EventDispatch | 3 |
| HitTest | 0.3 |
Custom scripts
There are no custom configured scripts.
PageXray
페이지에 대한 상세 정보입니다.
| 요약 | |
|---|---|
| HTTP 버전 | HTTP/1.1 |
| 전체 요청 횟수 | 90 |
| 전체 요청 도메인 수 | 9 |
| 전체 전송 사이즈 | 1.8 MB |
| 전체 콘텐츠 사이즈 | 2.3 MB |
| 압축되지 않은 애셋의 수 | 43 |
| 전체 로딩까지 걸린 시간 | 2477 ms |
| 상태코드별 응답 횟수 | |
|---|---|
| 200 | 89 |
| 204 | 1 |
파일 종류별 크기 및 요청 횟수
| 종류 | 헤더 용량 | 전송 용량 | 콘텐츠 용량 | 요청 횟수 |
|---|---|---|---|---|
| html | 482 B | 48.9 KB | 48.9 KB | 1 |
| css | 8.7 KB | 708.7 KB | 716.4 KB | 35 |
| javascript | 8.0 KB | 739.1 KB | 1.2 MB | 35 |
| image | 3.1 KB | 73.3 KB | 72.8 KB | 14 |
| font | 286 B | 198.1 KB | 197.8 KB | 2 |
| svg | 274 B | 7.4 KB | 7.4 KB | 1 |
| other | 492 B | 96.4 KB | 96.4 KB | 2 |
| 총합 | 21.3 KB | 1.8 MB | 2.3 MB | 90 |
도메인별 크기 및 요청 횟수
| 종류 | 헤더 용량 | 전송 용량 | 콘텐츠 용량 | 요청 횟수 |
|---|---|---|---|---|
| joomoney.fund | 21.3 KB | 1.6 MB | 1.6 MB | 78 |
| fonts.googleapis.com | N/A | 1.5 KB | 9.2 KB | 2 |
| cdnjs.cloudflare.com | N/A | 44.4 KB | 155.9 KB | 1 |
| www.google.com | N/A | 701 B | 762 B | 1 |
| connect.facebook.net | N/A | 59.1 KB | 231.3 KB | 2 |
| www.google-analytics.com | N/A | 17.5 KB | 42.7 KB | 2 |
| fonts.gstatic.com | N/A | 14.0 KB | 13.7 KB | 1 |
| www.gstatic.com | N/A | 92.1 KB | 280.4 KB | 1 |
| www.facebook.com | N/A | 438 B | 88 B | 2 |
캐시 관련 헤더 내용 분석
| 헤더 종류 | 최소 | 중간 | 최대 |
|---|---|---|---|
| Expires | 0 seconds | 0 seconds | 1 year |
| Last modified | 0 seconds | 27 weeks | 21 years |
| Cookies | 0 | 1 | 5 |
onLoad 이벤트 이후 발생한 요청
| 종류 | 전송 용량 | 요청 횟수 |
|---|---|---|
| html | N/A | 0 |
| css | N/A | 0 |
| javascript | N/A | 0 |
| image | 4.5 KB | 4 |
| font | N/A | 0 |
| 총합 | 4.5 KB | 4 |
onContentLoad 이벤트 이후 발생한 요청
onLoad 이벤트 이후에 발생한 요청을 포함합니다.
| 종류 | 전송 용량 | 요청 횟수 |
|---|---|---|
| html | N/A | 0 |
| css | N/A | 0 |
| javascript | N/A | 0 |
| image | 4.8 KB | 5 |
| font | N/A | 0 |
| 총합 | 4.8 KB | 5 |
Lighthouse (version 3.2.1)
Score
| Performance | Progressive Web App | Best Practices | Accessibility | SEO |
|---|---|---|---|---|
| 13 | 31 | 73 | 81 | 90 |
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.3 s | 4 |
First Contentful Paint marks the time at which the first text or image is painted. Learn more. | ||
| First Meaningful Paint | 8.3 s | 4 |
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,12.364491 | 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 | 8.3 s | 20 |
Speed Index shows how quickly the contents of a page are visibly populated. Learn more. | ||
| Estimated Input Latency | 60 ms | 89 |
The score above is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more. | ||
| Browser errors were logged to the console | 0 | |
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. | ||
| First CPU Idle | 10.9 s | 14.000000000000002 |
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 | 12.4 s | 15 |
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: No manifest was fetched, Site does not register a service worker. | ||
| 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: No manifest was fetched. | ||
| Address bar does not match brand colors | 0 | |
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched,
No | ||
| Minimize main-thread work | 3.9 s | 52 |
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.6 s | 84 |
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 310 ms | 74 |
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 360 ms | 72 |
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. | ||
| Links do not have a discernible name | 0 | |
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. | ||
| Serve static assets with an efficient cache policy | 84 resources found | 1 |
A long cache lifetime can speed up repeat visits to your page. Learn more. | ||
| Avoids enormous network payloads | Total size was 1,930 KB | 99 |
Large network payloads cost users real money and are highly correlated with long load times. Learn more. | ||
| Defer offscreen images | Potential savings of 34 KB | 88 |
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 5,550 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. | ||
| Minify CSS | Potential savings of 80 KB | 57.99999999999999 |
Minifying CSS files can reduce network payload sizes. Learn more. | ||
| Minify JavaScript | Potential savings of 49 KB | 75 |
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more. | ||
| Defer unused CSS | Potential savings of 667 KB | 8 |
Remove unused rules from stylesheets to reduce unnecessary bytes consumed by network activity. Learn more. | ||
| Serve images in next-gen formats | Potential savings of 46 KB | 75 |
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 27 KB | 75 |
Optimized images load faster and consume less cellular data. Learn more. | ||
| Enable text compression | Potential savings of 1,008 KB | 0 |
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more. | ||
| Links to cross-origin destinations are unsafe | 0 | |
Add | ||
| Includes front-end JavaScript libraries with known security vulnerabilities | 3 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 | 84 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. | ||
| Document does not have a meta description | 0 | |
Meta descriptions may be included in search results to concisely summarize page content. Learn more. | ||