Blog.me 네이버 블로그
blog.me Desktop Performance
56/100
These metrics represent real-world Chrome users experience viewing blog.me web page. Reports are focused on loading performance and other critical factors that most affect user experience. Follow our guide to track, optimize, and improve the quality of your web pages.
Metrics
First Contentful Paint13/100 2.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Largest Contentful Paint20/100 3.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
Speed Index39/100 2.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Time to Interactive87/100 2.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Cumulative Layout Shift100/100 0.011
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Total Blocking Time100/100 60 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Should Fix (17)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Serve images in next-gen formats
Potential savings of 1,223 KiB
1,200 ms
Properly size images
Potential savings of 1,048 KiB
960 ms
Avoid multiple page redirects
Potential savings of 380 ms
380 ms
Remove unused JavaScript
Potential savings of 161 KiB
250 ms
Efficiently encode images
Potential savings of 276 KiB
240 ms
Eliminate render-blocking resources
Potential savings of 220 ms
220 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Ensure text remains visible during webfont load
Serve static assets with an efficient cache policy
99 resources found
Avoid enormous network payloads
Total size was 4,512 KiB
Avoid an excessive DOM size
1,165 elements
Minimizes main-thread work
1.8 s
Avoid chaining critical requests
8 chains found
Largest Contentful Paint element
1 element found
User Timing marks and measures
3 user timings
Avoid large layout shifts
5 elements found
Avoid long main-thread tasks
7 long tasks found
Keep request counts low and transfer sizes small
126 requests • 4,512 KiB
Passed Audits (12)
Use video formats for animated content
Uses passive listeners to improve scrolling performance
JavaScript execution time
0.7 s
Avoids `document.write()`
Minify CSS
Initial server response time was short
Root document took 240 ms
Enable text compression
Potential savings of 9 KiB
Defer offscreen images
Potential savings of 215 KiB
Preload key requests
Remove unused CSS
Potential savings of 21 KiB
Preconnect to required origins
Minify JavaScript
blog.me Desktop SEO
73/100
These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking. Learn more. Run these additional validators on your site to check additional SEO best practices.
Should Fix (3)
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
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`
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Page is blocked from indexing
Passed Audits (8)
Document has a `<title>` element
robots.txt is valid
Links are crawlable
Document avoids plugins
Image elements have `[alt]` attributes
Page has successful HTTP status code
Links have descriptive text
Document has a valid `hreflang`
blog.me Desktop Best Practices
69/100
These checks highlight opportunities to improve the overall code health of blog.me page. Current recommendations will help to make your page fast and secure, to create a good user experience and to avoid deprecated technologies.
Should Fix (4)
Trust and Safety
Links to cross-origin destinations are unsafe
Includes front-end JavaScript libraries with known security vulnerabilities
13 vulnerabilities detected
Does not use HTTPS
2 insecure requests found
User Experience
Displays images with incorrect aspect ratio
Passed Audits (10)
Avoids deprecated APIs
Page has the HTML doctype
Avoids Application Cache
Serves images with appropriate resolution
Allows users to paste into password fields
No browser errors logged to the console
Avoids requesting the geolocation permission on page load
Detected JavaScript libraries
Properly defines charset
Avoids requesting the notification permission on page load
blog.me Desktop Progressive Web App
7/100
These checks validate the aspects of a Progressive Web App. Learn more. These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
Should Fix (12)
Fast and reliable
`start_url` does not respond with a 200 when offline
Current page does not respond with a 200 when offline
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 16.3 s
Installable
Does not register a service worker that controls page and `start_url`
Does not use HTTPS
2 insecure requests found
Web app manifest does not meet the installability requirements
PWA Optimized
Is not configured for a custom splash screen
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Manifest doesn't have a maskable icon
Does not provide fallback content when JavaScript is not available
Does not set a theme color for the address bar.
Does not provide a valid `apple-touch-icon`
Passed Audits (1)
Redirects HTTP traffic to HTTPS
blog.me Desktop Accessibility
92/100
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged. These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Should Fix (2)
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
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.
`[aria-*]` attributes do not match their roles
Passed Audits (22)
`[id]` attributes on active, focusable elements are unique
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`[role]`s are contained by their required parent element
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
The page contains a heading, skip link, or landmark region
Buttons have an accessible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
ARIA IDs are unique
`[aria-*]` attributes are valid and not misspelled
`[aria-*]` attributes have valid values
Links have a discernible name
`<html>` element has a valid value for its `[lang]` attribute
Heading elements appear in a sequentially-descending order
`[aria-hidden="true"]` is not present on the document `<body>`
Image elements have `[alt]` attributes
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
Form elements have associated labels
`[aria-hidden="true"]` elements do not contain focusable descendents
`<html>` element has a `[lang]` attribute
Desktop Speed
82/100
These checks analyze the performance of blog.me on desktop devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Should Fix (5)
Optimize images
Leverage browser caching
Enable compression
Minify JavaScript
Minify HTML
Passed Audits (5)
Avoid landing page redirects
Reduce server response time
Minify CSS
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Prioritize visible content
www.blog.com
www.blog.net
www.blog.org
www.blog.info
www.blog.biz
www.blog.us
www.blog.mobi
www.log.me
www.blog.me
www.vlog.me
www.bvlog.me
www.vblog.me
www.glog.me
www.bglog.me
www.gblog.me
www.hlog.me
www.bhlog.me
www.hblog.me
www.nlog.me
www.bnlog.me
www.nblog.me
www.bog.me
www.bpog.me
www.blpog.me
www.bplog.me
www.boog.me
www.bloog.me
www.bolog.me
www.bkog.me
www.blkog.me
www.bklog.me
www.blg.me
www.blig.me
www.bloig.me
www.bliog.me
www.blkg.me
www.blokg.me
www.bllg.me
www.blolg.me
www.bllog.me
www.blpg.me
www.blopg.me
www.blo.me
www.blof.me
www.blogf.me
www.blofg.me
www.blov.me
www.blogv.me
www.blovg.me
www.blot.me
www.blogt.me
www.blotg.me
www.blob.me
www.blogb.me
www.blobg.me
www.bloy.me
www.blogy.me
www.bloyg.me
www.bloh.me
www.blogh.me
www.blohg.me
www.blog.net
www.blog.org
www.blog.info
www.blog.biz
www.blog.us
www.blog.mobi
www.log.me
www.blog.me
www.vlog.me
www.bvlog.me
www.vblog.me
www.glog.me
www.bglog.me
www.gblog.me
www.hlog.me
www.bhlog.me
www.hblog.me
www.nlog.me
www.bnlog.me
www.nblog.me
www.bog.me
www.bpog.me
www.blpog.me
www.bplog.me
www.boog.me
www.bloog.me
www.bolog.me
www.bkog.me
www.blkog.me
www.bklog.me
www.blg.me
www.blig.me
www.bloig.me
www.bliog.me
www.blkg.me
www.blokg.me
www.bllg.me
www.blolg.me
www.bllog.me
www.blpg.me
www.blopg.me
www.blo.me
www.blof.me
www.blogf.me
www.blofg.me
www.blov.me
www.blogv.me
www.blovg.me
www.blot.me
www.blogt.me
www.blotg.me
www.blob.me
www.blogb.me
www.blobg.me
www.bloy.me
www.blogy.me
www.bloyg.me
www.bloh.me
www.blogh.me
www.blohg.me