Skip to content
https://merpaticerita.blogspot.com

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

93

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older 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 older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:5.214 source:map[column:29811 line:2 type:source-location url:https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.4/jquery.min.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:14.182 source:map[type:text value:[unattributed]]] map[reflowTime:0.48 source:map[column:406 line:74 type:source-location url:https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js urlProvider:network]] map[reflowTime:0.108 source:map[column:852 line:190 type:source-location url:https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js urlProvider:network]] map[reflowTime:0.354 source:map[column:17433 line:2 type:source-location url:https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.4/jquery.min.js urlProvider:network]] map[reflowTime:0.126 source:map[column:17516 line:2 type:source-location url:https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.4/jquery.min.js urlProvider:network]] map[reflowTime:0.092 source:map[column:19379 line:2 type:source-location url:https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.4/jquery.min.js urlProvider:network]] map[reflowTime:0.556 source:map[column:20126 line:3 type:source-location url:https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.4/jquery.min.js urlProvider:network]] map[reflowTime:2.934 source:map[column:18223 line:2 type:source-location url:https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.4/jquery.min.js urlProvider:network]] map[reflowTime:0.493 source:map[column:19305 line:3 type:source-location url:https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.4/jquery.min.js urlProvider:network]] map[reflowTime:0.659 source:map[column:13566 line:3 type:source-location url:https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.4/jquery.min.js urlProvider:network]] map[reflowTime:0.146 source:map[column:96 line:130 type:source-location url:https://pagead2.googlesyndication.com/pagead/managed/js/adsense/m202609290101/show_ads_impl_fy2021.js urlProvider:network]]]

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
article.blog-post > div.entry-image > a.entry-image-link > span.entry-thumb article.blog-post > div.entry-image > a.entry-image-link > span.entry-thumb
/img/b/R29vZ2xl/AVvXsEhpjYZ0z4TjU8dg7iIfVVrgFxcCsFok4OF0k...18.4 KiB14.8 KiB
article.blog-post > div.entry-image > a.entry-image-link > span.entry-thumb article.blog-post > div.entry-image > a.entry-image-link > span.entry-thumb
/img/b/R29vZ2xl/AVvXsEgXSSdn_TjoL6jlCun9txqCxEqwij-aG0iJC...14.1 KiB10.5 KiB
article.blog-post > div.entry-image > a.entry-image-link > span.entry-thumb article.blog-post > div.entry-image > a.entry-image-link > span.entry-thumb
/img/b/R29vZ2xl/AVvXsEgKPUzqEHUhILPJJ7SEB2qVth2B86OW1HQ7C...13.5 KiB9.8 KiB
article.blog-post > div.entry-image > a.entry-image-link > span.entry-thumb article.blog-post > div.entry-image > a.entry-image-link > span.entry-thumb
/img/b/R29vZ2xl/AVvXsEh3YYsn17IHoBA6hBoEqz20C28FXLxh0e_MD...10.5 KiB6.8 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
Merpati Balap dan Kalayang div#Header1 > div.header-widget > a.main-logo-img > img
/-Pd-y9pCKl54/XQOyd3IwEII/AAAAAAAABPs/hXCDzldmZEU2VBA9ZNg...
Merpati Balap dan Kalayang div.widget-content > div.footer-logo > a > img#Image150_img
/-Pd-y9pCKl54/XQOyd3IwEII/AAAAAAAABPs/hXCDzldmZEU2VBA9ZNg...
BeaverCheck Score div#HTML1 > div.widget-content > a > img
beavercheck.com/badge?url=https%3A%2F%2Fmerpaticerita.blogspot.com

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Max Potential First Input Delay 110 ms
●Layout shift culprits
●Document request latency
●Optimize DOM size
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 2,166 KiB
●JavaScript execution time 0.5 s
●Minimizes main-thread work 1.1 s
●Avoid long main-thread tasks 2 long tasks found
●Avoid non-composited animations 1 animated element found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 40 ms
●Server Backend Latencies 320 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 320 ms
●Avoid large layout shifts 11 layout shifts found
○INP breakdown
○LCP request discovery
○User Timing marks and measures
83

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
MENU div.headerify-fixed > div.headerify > div.container > a.menu-toggle
SEARCH div.headerify-fixed > div.headerify > div.container > a.search-toggle
by div.entry-header > div.entry-meta > span.entry-author > em
Sandi Arianto div.entry-header > div.entry-meta > span.entry-author > span.by
September 16, 2025 div.entry-header > div.entry-meta > span.entry-time > time.published
by div.entry-header > div.entry-meta > span.entry-author > em
Sandi Arianto div.entry-header > div.entry-meta > span.entry-author > span.by
February 28, 2024 div.entry-header > div.entry-meta > span.entry-time > time.published
by div.entry-header > div.entry-meta > span.entry-author > em
Sandi Arianto div.entry-header > div.entry-meta > span.entry-author > span.by
February 21, 2024 div.entry-header > div.entry-meta > span.entry-time > time.published
by div.entry-header > div.entry-meta > span.entry-author > em
Sandi Arianto div.entry-header > div.entry-meta > span.entry-author > span.by
February 21, 2024 div.entry-header > div.entry-meta > span.entry-time > time.published
by div.entry-header > div.entry-meta > span.entry-author > em
Sandi Arianto div.entry-header > div.entry-meta > span.entry-author > span.by
December 26, 2023 div.entry-header > div.entry-meta > span.entry-time > time.published
by div.entry-header > div.entry-meta > span.entry-author > em
Sandi Arianto div.entry-header > div.entry-meta > span.entry-author > span.by
May 29, 2022 div.entry-header > div.entry-meta > span.entry-time > time.published
by div.entry-header > div.entry-meta > span.entry-author > em
Sandi Arianto div.entry-header > div.entry-meta > span.entry-author > span.by
May 22, 2022 div.entry-header > div.entry-meta > span.entry-time > time.published
Load More Posts div#main > div#Blog1 > div#blog-pager > a#load-more-link

These are opportunities to improve the legibility of your content.

Internationalization and localization

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.ltr html.ltr

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#LinkList153 > ul.social > li.facebook > a.facebook div#LinkList153 > ul.social > li.facebook > a.facebook
div#LinkList153 > ul.social > li.youtube > a.youtube div#LinkList153 > ul.social > li.youtube > a.youtube
div#LinkList153 > ul.social > li.rss > a.rss div#LinkList153 > ul.social > li.rss > a.rss
div.blog-posts > article.blog-post > div.entry-image > a.entry-image-link div.blog-posts > article.blog-post > div.entry-image > a.entry-image-link
div.blog-posts > article.blog-post > div.entry-image > a.entry-image-link div.blog-posts > article.blog-post > div.entry-image > a.entry-image-link
div.blog-posts > article.blog-post > div.entry-image > a.entry-image-link div.blog-posts > article.blog-post > div.entry-image > a.entry-image-link
div.blog-posts > article.blog-post > div.entry-image > a.entry-image-link div.blog-posts > article.blog-post > div.entry-image > a.entry-image-link
div.blog-posts > article.blog-post > div.entry-image > a.entry-image-link div.blog-posts > article.blog-post > div.entry-image > a.entry-image-link
div.blog-posts > article.blog-post > div.entry-image > a.entry-image-link div.blog-posts > article.blog-post > div.entry-image > a.entry-image-link
div.blog-posts > article.blog-post > div.entry-image > a.entry-image-link div.blog-posts > article.blog-post > div.entry-image > a.entry-image-link
div.widget-content > ul.social-footer > li.facebook-f > a.facebook-f div.widget-content > ul.social-footer > li.facebook-f > a.facebook-f
div.widget-content > ul.social-footer > li.youtube > a.youtube div.widget-content > ul.social-footer > li.youtube > a.youtube
div.widget-content > ul.social-footer > li.rss > a.rss div.widget-content > ul.social-footer > li.rss > a.rss

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.

Best practices

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 about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has a valid value for its `[lang]` attribute
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

●Uses HTTPS
●Avoids deprecated APIs
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No browser errors logged to the console
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback