Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

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.

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.

	URL	Resource Size	Est Savings
Preview Markdown after pdf to md `a.surface-card > div.illus-frame > div.fill-c > img.illus-img`	pdftomd.tools/images/seo/how-preview.jpg	136.6 KiB	128.9 KiB
Extract text layers during pdf to md `a.surface-card > div.illus-frame > div.fill-c > img.illus-img`	pdftomd.tools/images/seo/how-extract.jpg	118.3 KiB	111.6 KiB
Drop a PDF for pdf to md conversion `a.surface-card > div.illus-frame > div.fill-c > img.illus-img`	pdftomd.tools/images/seo/how-drop.jpg	110.6 KiB	104.3 KiB
Example of a PDF page converted into Markdown output `div.home-container > div.grid > div.relative > img.block`	pdftomd.tools/images/seo/hero-pdf-to-md-v2.jpg	113.5 KiB	103.5 KiB
A browser window displaying a Markdown preview of a quarterly report with headi… `div.mx-auto > div > button.group > img.block`	pdftomd.tools/images/promo-poster.webp	48.9 KiB	47.0 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-3-IMG

nodeLabel: Example of a PDF page converted into Markdown output

path: 1,HTML,1,BODY,3,MAIN,3,DIV,0,DIV,0,DIV,1,DIV,0,IMG

selector: div.home-container > div.grid > div.relative > img.block

snippet: <img alt="Example of a PDF page converted into Markdown output" width="1280" height="720" decoding="async" data-nimg="1" class="block h-auto w-full rounded-3xl object-contain shadow-[0_28px_60px_-28px_r…" style="color:transparent" src="/images/seo/hero-pdf-to-md-v2.jpg">

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.

URL	Transfer Size
pdftomd.tools/_next/static/css/40b0a6515b989b9d.css	16.8 KiB
pdftomd.tools/boot.js?v=85f3080a1e	955 B
pdftomd.tools/_next/static/css/6cdac7a8c5bbabec.css	1.2 KiB

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

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.

●Time to Interactive 3.4 s

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 807 KiB

●JavaScript execution time 0.3 s

●Minimizes main-thread work 1.1 s

●Avoid long main-thread tasks 2 long tasks found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 60 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 30 ms

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

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
.tools `span.contents > a.inline-flex > span.wm > span.wm-tld`
Runs in your browser · nothing uploaded `div.flex > div.flex > span.flex > span`
15s product demo `div.home-container > section.home-section > div.mx-auto > span.eyebrow-pill`
A quarterly PDF report converts into formatted headings, text, and bullet point… `div.home-container > section.home-section > div.mx-auto > p.sec-sub`
Workflow `div.home-container > section.home-section > div.mx-auto > span.eyebrow-pill`
Four short steps, all inside this browser tab. `div.home-container > section.home-section > div.mx-auto > p.sec-sub`
Go to the tool `ol.mt-12 > li > a.surface-card > span.card-cta`
Go to the tool `ol.mt-12 > li > a.surface-card > span.card-cta`
Go to the tool `ol.mt-12 > li > a.surface-card > span.card-cta`
Reverse converter `ol.mt-12 > li > a.surface-card > span.card-cta`
Overview `div.grid > div > div > span.eyebrow-pill`
standardized as ISO 32000 `div > div.mt-5 > p > a.rlink`
John Gruber published in 2004 `div > div.mt-5 > p > a.rlink`
Preview `div.lg:pt-2 > figure.surface-card > div.mb-4 > span.chip-m`
Use cases `div > section.home-section > div.mx-auto > span.eyebrow-pill`
Where clean Markdown saves the most cleanup time. `div > section.home-section > div.mx-auto > p.sec-sub`
for-LLM scene page `div.mt-12 > a.surface-card > p.card-p > span.font-medium`
For-LLM scene page `section.home-section > div.mt-12 > a.surface-card > span.card-cta`
Obsidian scene page `div.mt-12 > a.surface-card > p.card-p > span.font-medium`
Obsidian scene page `section.home-section > div.mt-12 > a.surface-card > span.card-cta`
Python guide page `div.mt-12 > a.surface-card > p.card-p > span.font-medium`
Python guide `section.home-section > div.mt-12 > a.surface-card > span.card-cta`
Open the tool `section.home-section > div.mt-12 > a.surface-card > span.card-cta`
Local-first `div.grid > div.surface-card > div.flex > span.eyebrow-pill`
Read the privacy policy `div.grid > div.surface-card > div.mt-auto > a.inline-flex`
Other direction `div.grid > div.surface-card > div.flex > span.eyebrow-pill`
Tool suite `div > section.home-section > div.mx-auto > span.eyebrow-pill`
Focused pages for the next step, each one a click away. `div > section.home-section > div.mx-auto > p.sec-sub`
A standalone converter page with the same local engine. `div.mt-12 > a.surface-card > span.min-w-0 > span.tool-desc`
Run the conversion locally, without uploading anything. `div.mt-12 > a.surface-card > span.min-w-0 > span.tool-desc`
Turn Markdown back into a printable document. `div.mt-12 > a.surface-card > span.min-w-0 > span.tool-desc`
Render notes or a README as a clean print layout. `div.mt-12 > a.surface-card > span.min-w-0 > span.tool-desc`
Keep headings, lists and tables intact when converting files. `div.mt-12 > a.surface-card > span.min-w-0 > span.tool-desc`
Prepare tidy text before you paste it into a chat model. `div.mt-12 > a.surface-card > span.min-w-0 > span.tool-desc`
Bring documents into a vault with headings intact. `div.mt-12 > a.surface-card > span.min-w-0 > span.tool-desc`
Script the same job locally with common Python libraries. `div.mt-12 > a.surface-card > span.min-w-0 > span.tool-desc`
— Daring Fireball `ol.mt-4 > li.flex > span > span`
, 2004 `ol.mt-4 > li.flex > span > span`
— ISO `ol.mt-4 > li.flex > span > span`
, 2020 `ol.mt-4 > li.flex > span > span`
— GitHub `ol.mt-4 > li.flex > span > span`
— Mozilla `ol.mt-4 > li.flex > span > span`
Questions `div > section#faq > div.mx-auto > span.eyebrow-pill`
Short answers on privacy, scans, and tables. `div > section#faq > div.mx-auto > p.sec-sub`
.tools `div > a.inline-flex > span.wm > span.wm-tld`
Free in-browser PDF ↔ Markdown conversion. Files stay on your device for the on… `div.grid > div.col-span-3 > div > p.mt-2`
Reverse converter `div.col-span-3 > div > p.mt-4 > a.font-medium`
Contact: we do not publish an email address yet. `div.grid > div.col-span-3 > div > p.mt-3`
ChatGPT `div.col-span-3 > div.mt-5 > div.mt-2 > a.ask-a`
Perplexity `div.col-span-3 > div.mt-5 > div.mt-2 > a.ask-a`
Claude `div.col-span-3 > div.mt-5 > div.mt-2 > a.ask-a`
Gemini `div.col-span-3 > div.mt-5 > div.mt-2 > a.ask-a`
Grok `div.col-span-3 > div.mt-5 > div.mt-2 > a.ask-a`
豆包 `div.col-span-3 > div.mt-5 > div.mt-2 > a.ask-a`
DeepSeek `div.col-span-3 > div.mt-5 > div.mt-2 > a.ask-a`
Kimi `div.col-span-3 > div.mt-5 > div.mt-2 > a.ask-a`
PDF to MD `div > ul.mt-4 > li > a.foot-link`
MD to PDF `div > ul.mt-4 > li > a.foot-link`
Converter `div > ul.mt-4 > li > a.foot-link`
Convert PDF to MD `div > ul.mt-4 > li > a.foot-link`
Markdown to PDF `div > ul.mt-4 > li > a.foot-link`
Batch `div > ul.mt-4 > li > a.foot-link`
For LLM `div > ul.mt-4 > li > a.foot-link`
Obsidian `div > ul.mt-4 > li > a.foot-link`
Python `div > ul.mt-4 > li > a.foot-link`
Blog `div > ul.mt-4 > li > a.foot-link`
About `div > ul.mt-4 > li > a.foot-link`
Privacy `div > ul.mt-4 > li > a.foot-link`
Terms `div > ul.mt-4 > li > a.foot-link`
LLMs.txt `div > ul.mt-4 > li > a.foot-link`
English `div.mx-auto > div.mt-10 > nav.flex > a.foot-link`
Deutsch `div.mx-auto > div.mt-10 > nav.flex > a.foot-link`
Français `div.mx-auto > div.mt-10 > nav.flex > a.foot-link`
Español `div.mx-auto > div.mt-10 > nav.flex > a.foot-link`
Italiano `div.mx-auto > div.mt-10 > nav.flex > a.foot-link`
Português `div.mx-auto > div.mt-10 > nav.flex > a.foot-link`
Nederlands `div.mx-auto > div.mt-10 > nav.flex > a.foot-link`
日本語 `div.mx-auto > div.mt-10 > nav.flex > a.foot-link`
한국어 `div.mx-auto > div.mt-10 > nav.flex > a.foot-link`
简体中文 `div.mx-auto > div.mt-10 > nav.flex > a.foot-link`
繁體中文 `div.mx-auto > div.mt-10 > nav.flex > a.foot-link`
© 2026 pdftomd.tools team. Built for developers and technical writers. `body.font-sans > footer.border-t > div.mx-auto > p.mt-10`

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.tool-card > div.grid > div.flex > input.sr-only `div.tool-card > div.grid > div.flex > input.sr-only`

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Drop a PDF here, or click to browse Text PDFs only. Scans need OCR, which this… `div.tool-card > div.grid > div.flex > div.h-[300px]`
Install App `main.min-h-[70vh] > div.pointer-events-none > div.group > button.inline-flex`

○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

●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

●`[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

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`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

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●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.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[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 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 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

○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.

○`<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.

○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

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

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`