Skip to content
https://pastebin.com

Lighthouse Mobile

· 0 checks — Mobile 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.

75

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 long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
pastebin.com/themes/pastebin/js/vendors.bundle.js?30d6ece6979ee0cf553114400.0 s73.2 KiB
pastebin.com/themes/pastebin/sprite/spritesheet.webp14400.0 s46.1 KiB
pastebin.com/assets/9ce1885/jquery.min.js14400.0 s33.4 KiB
pastebin.com/assets/ff2ff0b/js/select2.full.min.js14400.0 s24.4 KiB
pastebin.com/themes/pastebin/css/app.bundle.css?30d6ece6979ee0cf553114400.0 s23.2 KiB
pastebin.com/assets/c80611c4/css/bootstrap.min.css14400.0 s22.8 KiB
pastebin.com/themes/pastebin/js/app.bundle.js?30d6ece6979ee0cf553114400.0 s12.4 KiB
pastebin.com/themes/pastebin/img/pastebin_logo_side_outline_support_ukraine.webp14400.0 s9.5 KiB
pastebin.com/assets/f04f76b8/yii.activeForm.js14400.0 s7.9 KiB
pastebin.com/assets/f04f76b8/yii.js14400.0 s6.2 KiB
pastebin.com/assets/d65ff796/dist/bootstrap-tagsinput.js14400.0 s5.7 KiB
pastebin.com/themes/pastebin/img/hello.webp14400.0 s2.6 KiB
pastebin.com/assets/ff2ff0b/css/select2.min.css14400.0 s2.3 KiB
pastebin.com/themes/pastebin/img/info.png14400.0 s1.7 KiB
pastebin.com/assets/c19c6973/js/select2-krajee.min.js14400.0 s1.5 KiB
pastebin.com/themes/pastebin/img/close_promo.png14400.0 s1.5 KiB
pastebin.com/assets/c19c6973/css/select2-default.min.css14400.0 s1.1 KiB
pastebin.com/assets/fb16b45a/img/loading-plugin.gif14400.0 s931 B
pastebin.com/themes/pastebin/img/guest.webp14400.0 s911 B
pastebin.com/themes/pastebin/css/vendors.bundle.css?30d6ece6979ee0cf553114400.0 s500 B
pastebin.com/assets/d65ff796/dist/bootstrap-tagsinput.css14400.0 s467 B
pastebin.com/assets/fb16b45a/js/kv-widgets.min.js14400.0 s460 B
pastebin.com/assets/fb16b45a/css/kv-widgets.min.css14400.0 s457 B
pastebin.com/assets/c19c6973/css/select2-addl.min.css14400.0 s446 B

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:75.488 source:map[type:text value:[unattributed]]]]

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.

URLTransfer SizeDuration
cdnjs.cloudflare.com/ajax/libs/codemirror/5.58.2/theme/material-darker.min.css1015 B789 ms
cdnjs.cloudflare.com/ajax/libs/codemirror/5.58.2/codemirror.min.css2.0 KiB789 ms
pastebin.com/themes/pastebin/css/app.bundle.css?30d6ece6979ee0cf553123.2 KiB450 ms
pastebin.com/themes/pastebin/css/vendors.bundle.css?30d6ece6979ee0cf5531500 B
pastebin.com/assets/c80611c4/css/bootstrap.min.css22.8 KiB450 ms
pastebin.com/assets/d65ff796/dist/bootstrap-tagsinput.css467 B
pastebin.com/assets/c19c6973/css/select2-addl.min.css446 B
pastebin.com/assets/fb16b45a/css/kv-widgets.min.css457 B
pastebin.com/assets/ff2ff0b/css/select2.min.css2.3 KiB
pastebin.com/assets/c19c6973/css/select2-default.min.css1.1 KiB

Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.

Why this matters

Performance issues directly impact user engagement and conversion rates.
head > meta head > meta

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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.

Estimated savings: 40 ms 41.7 KiB
URLTransfer SizeEst Savings
pastebin.com/assets/c80611c4/css/bootstrap.min.css22.7 KiB21.8 KiB
pastebin.com/themes/pastebin/css/app.bundle.css?30d6ece6979ee0cf553123.2 KiB19.8 KiB

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.

Estimated savings: 670 ms 155.8 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtag/js?id=G-S72LBY47R8151.5 KiB64.1 KiB
pastebin.com/themes/pastebin/js/vendors.bundle.js?30d6ece6979ee0cf553173.2 KiB47.7 KiB
cdnjs.cloudflare.com/ajax/libs/codemirror/5.58.2/codemirror.min.js48.8 KiB44.0 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 11.0 KiB
URLTransfer SizeEst Savings
pastebin.com/assets/f04f76b8/yii.activeForm.js7.8 KiB4.7 KiB
pastebin.com/assets/f04f76b8/yii.js6.2 KiB3.9 KiB
pastebin.com/assets/d65ff796/dist/bootstrap-tagsinput.js5.6 KiB2.5 KiB

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

●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Minify CSS
●Avoids enormous network payloads Total size was 498 KiB
●User Timing marks and measures 5 user timings
●JavaScript execution time 0.9 s
●Minimizes main-thread work 1.8 s
●Avoid long main-thread tasks 9 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 10 ms
●Server Backend Latencies 30 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 210 ms
○INP breakdown
○LCP request discovery
○Avoid non-composited animations
○Avoid large layout shifts
87

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.

ARIA

When an input field 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 more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-sm-9 > span.select2 > span.selection > span.select2-selection div.col-sm-9 > span.select2 > span.selection > span.select2-selection
span.select2 > span.selection > span.select2-selection > span#select2-postform-folder_key-container span.select2 > span.selection > span.select2-selection > span#select2-postform-folder_key-container

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.

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
NEW div.post-form__left > div.form-group > label.control-label > span.badge-new
NEW div.post-form__left > div.form-group > div.col-sm-9 > span.badge-new
create new paste div.container > div.footer__container > div.footer__left > a
syntax languages div.container > div.footer__container > div.footer__left > a
archive div.container > div.footer__container > div.footer__left > a
faq div.container > div.footer__container > div.footer__left > a
tools div.container > div.footer__container > div.footer__left > a
night mode div.container > div.footer__container > div.footer__left > a
api div.container > div.footer__container > div.footer__left > a
scraping api div.container > div.footer__container > div.footer__left > a
news div.container > div.footer__container > div.footer__left > a
pro div.container > div.footer__container > div.footer__left > a.pro
privacy statement div.container > div.footer__container > div.footer__left > a
cookies policy div.container > div.footer__container > div.footer__left > a
terms of service div.container > div.footer__container > div.footer__left > a
security disclosure div.container > div.footer__container > div.footer__left > a
dmca div.container > div.footer__container > div.footer__left > a
report abuse div.container > div.footer__container > div.footer__left > a
contact div.container > div.footer__container > div.footer__left > a

These are opportunities to improve the legibility of your content.

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.container > div.header__container > div.header__left > a.header__btn div.container > div.header__container > div.header__left > a.header__btn

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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Deprecated ARIA roles were not used
●The page contains a heading, skip link, or landmark region
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` 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
○`<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
○Heading elements appear in a sequentially-descending order
○`<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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
○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 DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
92

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.

Crawling and Indexing

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
div.lb-outerContainer > div.lb-container > div.lb-loader > a.lb-cancel div.lb-outerContainer > div.lb-container > div.lb-loader > a.lb-cancel
div.lb-dataContainer > div.lb-data > div.lb-closeContainer > a.lb-close div.lb-dataContainer > div.lb-data > div.lb-closeContainer > a.lb-close

To appear in search results, crawlers need access to your app.

○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
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback