Free read · outside-in
motohorek.life
Report/r/724c6e4059f6
Published by the site owner, who proved control of motohorek.life on 2026-11-17.
23 of 85 checks need work
3 fail·20 weak·62 pass
49 is Lighthouse's score for speed on this page. It counts nothing above, and a page can score 100 there and still fail 23 checks here.
What each layer scored
- Server runtime one check0/10%
- AI search2/540%
- Security headers6/1155%
- Email and DNS3/560%
- On-page basics25/4260%
- Discovery and AI readiness4/667%
- Doors a scanner knocks on7/978%
- Crawlability and indexation6/6100%
The short version
Three things are broken.
The first image waits to load, and images below it do not.
Also worth a look: llms.txt maps real pages, who says it, in JSON-LD, page titles, meta descriptions, one H1 per page, and 17 more, which fall into 12 in on-page basics, 2 in security headers, 1 in AI search, 1 in email and DNS, 1 in server runtime.
Section 02 lists every check, what it found, and what closes it.
Read from the outside. Nothing on the site was changed, and we did not log in.
Of 85 checks, 3 fail and 20 are weak. Failing: Above the fold eager, below it lazy, llms.txt maps real pages and Who says it, in JSON-LD. This reads the instructions your site sends to browsers and mail servers, not the quality of what you make. Every check behind the three check figures is in section 02.
A visitor on a mid-range phone waits 6.7 s before the main content appears, and the page asks them to download 1.02 MB to see it.
01Change since the last audit
What changed since your last audit
Nothing changed that this audit measures: the sitemap lists the same addresses as it did on 13 November 2026, and the tracking container and the response headers are unchanged.
02Everything we checked
What you can fix yourself, without us
85 checks across 9 layers. A FAIL is something a scanner can act on. A WARN is a door that is common but does not need to be open.
- Email authentication needs work: the DKIM key is 1024 bits, and 2048 is the minimum.
- Give each page one H1 that says what the page is about.
- Write a meta description of 120 to 160 characters; it is the sentence search results show.
- Add the missing security headers (HSTS, CSP, Referrer-Policy, framing protection). They are free and they close the cheap attacks.
- Turn on compression for the HTML.
- Publish or repair an llms.txt: a short markdown map of your best pages, so AI assistants quote you accurately.
These are free, and you are welcome to do them with a developer you already trust. If that is enough, this audit has done its job.
Not requested: the PII audit. Nothing in this report says anything about it.
| Check | State | What it is, and what closes it |
|---|---|---|
| Discovery and AI readinessall 6 pass | ||
| 6 passed XML sitemap, Pages read, Sitemap named in robots.txt, Favicon, Web app manifest, RSS feed. | ||
| Crawlability and indexationall 6 pass | ||
| 6 passed Search engines allowed, Indexable, Canonical tags, HTTP redirects to HTTPS, www and bare domain agree, Missing pages return 404. | ||
| On-page basics16 of 42 need work | ||
| Above the fold eager, below it lazy | FAIL | 1 above-the-fold image(s) lazy-loaded (97421167); 1 below-the-fold image(s) loaded eagerly (IMG_1060-768x576.jpeg), so the page delays what a visitor sees and fetches what they may never reach.97421167; IMG_1060-768x576.jpegLazy-load below-the-fold images and load the hero eagerly. |
| Page titles | WARN | 1 of 15 pages are missing a title or run past 65 characters; the longest is 87 on /Camino Distinto Travel Blog - Жизнь в путешествии: 14 лет в дороге, 57Give every page a unique title under 60 characters naming the page. |
| Meta descriptions | WARN | 1 of 15 pages are missing a description or sit outside 80 to 200 characters/ 217Write a 120 to 160 character description naming the page's subject. |
| One H1 per page | WARN | 1 of 15 pages do not: 0 on /Use one H1 per page, near the top, matching the page's subject. |
| Social preview tags | WARN | 1 of 15 pages lack an og:title or an og:imageAdd og:title, og:description and og:image to every page. |
| Compressed transfer | WARN | the home page arrived with no content-encoding, so every visitor downloads it wholeno content-encoding header on the home pageEnable Brotli or gzip for HTML, CSS and JavaScript at the edge. |
| Titles too long to show | WARN | 1 of 15 titles run past 65 characters and are cut off in a result/Shorten these titles to under 60 characters. |
| Descriptions too long | WARN | 1 of 15 descriptions run past 200 characters and are cut off/Cut these descriptions to under 160 characters. |
| Pages with no H1 | WARN | 1 of 15 pages have no H1, so nothing states what the page is about/Add one H1 to every page, near the top. |
| Pages with no social image | WARN | 1 of 15 pages would share without an image or a title/Add an og:image at least 1200 by 630 to every shareable page. |
| Images with no alt text | WARN | 7 of 15 pages have images without alt text/2020/02/isla-baru-colombia/, /2020/05/cafayate-canyon-argentina/, /2020/07/punta-de-choros-chile/Add alt text to these images, or mark decorative ones alt="". |
| Image formats | WARN | 11 legacy image(s) against 0 modern one(s)/wp-content/uploads/2023/03/6827AA75-19C0-4F0F-994E-2AE48CD1FCF6.jpeg |
| Inline scripts on the home page | WARN | 9 inline scripts, each one blocking the parser9Move inline scripts to files so they cache and CSP can govern them. |
| Text to markup | WARN | 6% of the page is words, so a reader waits for markup7082 characters of text in 111785 bytesReplace image-only or script-heavy markup with the text it stands for. |
| Page weight | WARN | 2560 KB over 21 request(s)2560 KB, 21 requestsCut page weight: compress images and drop scripts you do not use. |
| Smallest image format the site supports | WARN | No image is served as WebP or AVIF, and IMG_9288-768x558.jpeg is a 232 KB JPEG photograph; re-encoded it would weigh about 81 KB.IMG_9288-768x558.jpeg 232 KB; IMG_0755-768x576.jpeg 192 KB; IMG_5907-768x576.jpeg 146 KBRe-encode these images as WebP or AVIF and drop the PNG photographs. |
| 26 passed Structured data, Image alt text, Page language declared, Mobile viewport, Cache policy on the page itself, Mixed content, Duplicate page titles, Pages with no title, Pages with no description, Descriptions too short, Pages with more than one H1, Pages with no canonical, Canonicals pointing elsewhere, Standards mode, Character encoding declared, Encoding in the response header, Twitter card tags, Language alternatives declared, Internal links on the home page, Resource hints, URLs are short and readable, Time to first byte, Third-party hosts, Images served at the width they render, Cache validators, Vary on encoding. | ||
| Security headers2 of 11 need work | ||
| HSTS | WARN | max-age=86400Send Strict-Transport-Security for a year with includeSubDomains. |
| Content Security Policy | WARN | present but script-src allows inline or evaldefault-src 'self'; img-src 'self' data: https:; style-src 'self' 'unsafe-inlineSend Content-Security-Policy in report-only first, then enforce it. |
| 9 passed HSTS preload, Legacy XSS header, security.txt, MIME sniffing blocked, Clickjacking protection, Referrer policy, Permissions policy, Cross-origin opener policy, Server banner. | ||
| Email and DNS1 of 5 need work | ||
| DKIM | WARN | key on zmail, 1024-bit (2048 is the current minimum)Publish the DKIM key your mail provider issues. |
| 4 passed Receives email at the domain, SPF, DMARC, Branded email. | ||
| Doors a scanner knocks onall 9 pass | ||
| 9 passed What the site runs, Version disclosed in markup, readme.html, Author names via API, XML-RPC, Login page, Uploads listing, Debug log, .env file. | ||
| Server runtime1 of 1 need work | ||
| PHP runtime | WARN | PHP is in the request path, because this is a WordPress site, and the version is not disclosed from outside, so it cannot be checked from here. During the current PHP2Shell emergency that is not a pass: ask the host which branch and version the pool runs, and whether it is on 8.2.35, 8.3.36, 8.4.27 or 8.5.12.Run a supported PHP branch and hide the version. |
| AI search3 of 5 need work | ||
| llms.txt maps real pages | FAIL | There is no /llms.txt, so an answer engine has nothing but the pages to read.GET /llms.txt answered 404Publish /llms.txt, or extend it: the site name, then one line per important page. |
| Who says it, in JSON-LD | FAIL | The page's JSON-LD describes collectionpage, breadcrumblist, website, but no Organization or LocalBusiness, so there is no entity behind the words.Add Organization JSON-LD with name, url and two sameAs links that resolve. |
| An answer block where a searcher lands | WARN | 1 of 4 pages carry an answer block; none on /, /newsletter-ru/, /en/./, /newsletter-ru/, /en/, /en/shop/Add a 40 to 90 word answer under the H1 that begins with the question. |
| 2 passed Crawler rules for answer engines, Every claim of freshness is checkable. | ||
no container found in the HTML. A container is optional: this says nothing about the site tracking you, only that this page loads no tag manager.
03What we measured
The pages we read
| Page | Title | H1 | Description | Canonical | Alt text |
|---|---|---|---|---|---|
| / | 87 ch | 0 | 217 ch | self | 100% |
| /2019/08/13-unique-animals-in-amazon-jungle-to-see-without-tour/ | 57 ch | 1 | 126 ch | self | 100% |
| /2019/11/ingapirka/ | 34 ch | 1 | 135 ch | self | 100% |
| /2020/02/isla-baru-colombia/ | 48 ch | 1 | 104 ch | self | 82% |
| /2020/05/cafayate-canyon-argentina/ | 48 ch | 1 | 162 ch | self | 83% |
| /2020/07/punta-de-choros-chile/ | 33 ch | 1 | 119 ch | self | 98% |
| /2020/12/workaway/ | 55 ch | 1 | 137 ch | self | 95% |
| /2021/04/fes/ | 38 ch | 1 | 130 ch | self | 91% |
| /2021/11/istanbul-route-vefa-to-balat/ | 43 ch | 1 | 132 ch | self | 98% |
| /2022/10/costa-rican-cuisine/ | 37 ch | 1 | 113 ch | self | 100% |
| /2023/04/kakamega-kenya/ | 39 ch | 1 | 118 ch | self | 100% |
| /2023/09/nacionalnyj-park-lovchen/ | 37 ch | 1 | 139 ch | self | 100% |
| /2024/11/samaya-vysokogornaya-stolica-mira/ | 49 ch | 1 | 123 ch | self | 100% |
| /en/2023/01/patagonia-an-ultimate-guide/ | 30 ch | 1 | 134 ch | self | 96% |
| /sotrudnichestvo/ | 14 ch | 1 | 127 ch | self | 100% |
Every check below ran on every page in this table, and each finding names the worst page it found it on.
Speed, measured by Lighthouse
Lighthouse 13.5.0, mobile, run on a real browser
Measured from a server in Helsinki, Finland, using a simulated mid-range phone on a mobile connection. Where that server sits is part of the score: visitors closer to it see faster times than visitors further away, so a site with customers on the other side of the world can score lower here than it feels in practice. Every audit is measured from the same place, which is what lets you compare one report against another. One run also moves by a few points on its own, so treat a change as real only when it repeats.
| Biggest single wins | Time | Bytes |
|---|---|---|
| Reduce unused JavaScript | 610 ms | |
| Initial server response time was short | 51 ms |
Lighthouse's own estimates for this page. They describe where the time goes, not what a rebuild costs.
Lighthouse
- Performance49
- Accessibility100
- Best practices77
- SEO100
- Largest paint6.7 s
- Page weight1045 KB
What would buy the most, in milliseconds:
- Reduce unused JavaScript610 ms
- Initial server response time was short51 ms
Lighthouse 13.5.0, mobile, run on a real browser.
AI search
Whether a machine that reads pages to answer a question can find the answer here, tell who says it, and quote it without distortion. It measures this page and the files around it; it does not promise a ranking, a citation or traffic in any assistant.
- FAIL llms.txt maps real pagesThere is no /llms.txt, so an answer engine has nothing but the pages to read.GET /llms.txt answered 404 Fix Publish /llms.txt, or extend it: the site name, then one line linking each important page.
- WARN An answer block where a searcher lands1 of 4 pages carry an answer block; none on /, /newsletter-ru/, /en/./, /newsletter-ru/, /en/, /en/shop/ Fix Add a 40 to 90 word answer under a question heading on the home page.
- FAIL Who says it, in JSON-LDThe page's JSON-LD describes collectionpage, breadcrumblist, website, but no Organization or LocalBusiness, so there is no entity behind the words. Fix Add Organization JSON-LD with name, url and two sameAs profiles.
- OK Crawler rules for answer enginesThe star group disallows . no answer-engine reader is named; none blocked by name; no Content-Signal line.no Content-Signal line
- OK Every claim of freshness is checkableThe page states 2025-04-23, and the sitemap carries no contradicting date.2025-04-23
2 of 5 checks pass.
The numbers above, drawn. Each one shows how it is on the left and what it should be on the right.
A visitor waits 6.7 s before the main content appears
The page asks for 1045 KB and paints its main content after 6.7 s, measured on a mid-range phone.
0 s6.7 s
That is what a new visitor sees: an empty screen, then the page. The score above is this, once.
The page has no headline at all
Measured on /: 1 of 15 pages do not: 0 on / /
what a reader sees
5 самых красивых (и опасных) колодцев Индии
Парк Рантамбор: сафари с тиграми в Индии
Как мы стали гостями на буддийском празднике | Вьетнам
Красный форт в Агре — наследие ЮНЕСКО в Индии
Тадж-Махал закроют для туристов? Чудо света в опасности
Полный гид по Тадж-Махалу: лайфхаки и честный отзыв
what the crawler reads
<h2> 5 самых красивых (и опасных) колодцев Индии <h2> Парк Рантамбор: сафари с тиграми в Индии <h2> Как мы стали гостями на буддийском празднике | Вьетнам <h2> Красный форт в Агре — наследие ЮНЕСКО в Индии <h2> Тадж-Махал закроют для туристов? Чудо света в опасности <h2> Полный гид по Тадж-Махалу: лайфхаки и честный отзыв (0 h1 on this page)
A reader sees a page with a title. A crawler sees this list, and picks one of them as the page's subject.
This report read 15 of 493 pages
Everything below is measured on those 15. The other 478 were not opened, so nothing here speaks for them.
A sample is a sample. The claim is what was read, never the whole site.
04The next step
This pass read 15 pages. The whole site crawl is free: every page, every internal link, and an inventory you can hand to a developer. It asks for an address, and the report is a link that keeps working after you close the tab.
This site has proved control, so it can carry these marks. Tap one for the code.
Badge for your own site: <a href="https://zpe.vc/audit/r/724c6e4059f6"><img src="https://zpe.vc/audit/b/724c6e4059f6.svg" width="220" height="52" alt="Audited outside-in, motohorek.life"></a>
Want the deeper report, the half that needs read-only access to your server? Ask for it.
05Limits and help
Where we could help
- Email: a mailbox on your own domain, aliases for hello, sales and billing, and SPF, DKIM and DMARC set up and tested.
- Security hardening: the headers this audit found missing, set and tested.
- On-page basics: titles, descriptions, headings and alt text, written per page rather than templated.
- A migration: the site as static files on Cloudflare's edge, with the editing workflow kept or replaced entirely.
What this audit cannot see
It ran without server access, so it cannot see plugin versions, the database, backups, logs, or your invoices. Three measurements a Worker cannot make are also absent rather than guessed: TLS certificate details, the HTTP protocol version, and whether the origin compresses. So is the PHP version under your site, unless the server volunteers it in a response header, which none of the twenty-two sites we sampled did. That layer is worth naming because two remote code execution flaws in PHP itself are being exploited in the wild as of 21 October 2026, and no scanner outside your server can see whether you are patched. They are in the deeper report.
The launch gate, read against this site
Our own pre-launch gate: fourteen gates and 110 lines, the list every site of ours is walked through before it serves a stranger. This is not that list repeated as advice. It is the part one reading from outside can settle, with the rest named and the reason it cannot. 16 settled, 8 not met, 24 of the 110 lines checkable this way.
1. it answers, everywhere, correctly 4 of 5 settled
- settled Unknown paths answer a deliberate 404, never a stack trace real 404
- settled One canonical host: apex and www agree both end at motohorek.life
- settled HTTPS is the way in yes
- not met One h1, headings in order One H1 per page: 1 of 15 pages do not: 0 on /
- settled Alt text on every image every page with images describes at least 80% of them
- cannot be seen from outside mixed content, what a browser fetches at load, the page with JavaScript off, the layout at 390 and 1280, the redirect map of old addresses, and whether a preview worker still shows a mock these need a browser running the page, or the tree the site was built from
2. the copy is defensible none of it can be settled here
- cannot be seen from outside every line of it: whether a claim traces to a source, whether a promise is regulated, whether the proof is real, and whether the price is shown a reading measures what a page says, not whether it is true; this gate is the owner's own, and the answers are paperwork
3. money and legal none of it can be settled here
- cannot be seen from outside the payment rail in live mode, refunds, terms, privacy, consent, labels, filings and retention each is a decision with a document behind it, and none of it is visible from one request
4. measurement, before the first visitor none of it can be settled here
- cannot be seen from outside whether analytics was proven by a real visit, the conversion event, the UTM convention, Search Console, the alert path, and the number read weekly the audit can find a tracking container; it cannot read the store it writes to
5. discovery, so the site can be found and described 5 of 9 settled
- settled robots.txt answers and points at the sitemap 1 Sitemap line(s)
- settled Sitemap answers, and the pages in it are the site's own routes found at /sitemap_index.xml
- settled robots.txt does not disallow the pages that matter no site-wide block
- settled A canonical tag on the page self-referencing and absolute on all 15 pages read
- settled Structured data parses and validates JSON-LD on every page read
- not met A unique title, within 60 characters Page titles: 1 of 15 pages are missing a title or run past 65 characters; the longest is 87 on /
- not met A unique description, within 155 characters Meta descriptions: 1 of 15 pages are missing a description or sit outside 80 to 200 characters
- not met A share card: og:title, og:description, og:image, twitter:card Social preview tags: 1 of 15 pages lack an og:title or an og:image
- not met llms.txt at the root llms.txt maps real pages: There is no /llms.txt, so an answer engine has nothing but the pages to read.
- cannot be seen from outside hreflang pairs, whether the share card renders on X, LinkedIn, WhatsApp, Telegram and Slack, the AI crawler policy chosen in robots.txt, whether the money page is two clicks from the root, the backlink list, and a link check over the whole built tree cards and policy choices are decisions, and the render check needs five other companies' surfaces
6. security audit 4 of 6 settled
- not met HSTS, with a year and includeSubDomains HSTS: max-age=86400
- not met A Content Security Policy on the response Content Security Policy: present but script-src allows inline or eval
- settled MIME sniffing blocked nosniff
- settled A referrer policy strict-origin-when-cross-origin
- settled Clickjacking protection frame-ancestors in CSP
- settled A permissions policy geolocation=(), microphone=(), camera=(), payment=()
- cannot be seen from outside whether the CSP still allows unsafe-inline somewhere, the dependency audit, the secret scan over the tree and the bundle, the rate limits, server-side validation, what an error response says, PII in logs, the backup and its restore, and who holds the deploy credential each needs the tree, the logs, or the account, and a response header is the only part of this gate that faces outward
7. page and accessibility audit 1 of 1 settled
- settled Speed measured on a throttled phone, not estimated measured, and the score is in this report
- cannot be seen from outside an axe scan with zero serious findings, the keyboard pass, contrast on every pair, the performance budget as a number to fail, images at the size they render, self-hosted fonts, HTML validity, and the page in print one of these needs a headless browser with a network profile, and the rest need a person with a keyboard
8. email 2 of 3 settled
- settled SPF published for the sending domain one record, ends in -all
- not met DKIM published DKIM: key on zmail, 1024-bit (2048 is the current minimum)
- settled DMARC published policy p=reject
- cannot be seen from outside a real message read in Gmail, Outlook and Yahoo, the authentication results from the received headers, every transactional path, the reply path, unsubscribe, bounces, and the list export the DNS records face outward and are read here; the message itself needs an inbox
9. form and signup testing none of it can be settled here
- cannot be seen from outside the happy path with a read-back from the store, bad input, duplicates, spam, the rate limit, the confirmation, the mobile keyboard, and the removal path a form that writes into a hole looks identical to a working one from outside
10. load and stress none of it can be settled here
- cannot be seen from outside the capacity number, the load test at 1x, 5x and 10x, the breaking point, how it fails, and the cost at 10x the audit makes one request at a time, which is the opposite of a load test
11. operations, so a bad day is survivable none of it can be settled here
- cannot be seen from outside uptime and certificate-expiry alerting, the incident runbook, the rollback and its drill, scheduled backups with a tested restore, DNS TTL, log retention, and where the credentials live these are the owner's arrangements, not the site's behaviour
12. launch day none of it can be settled here
- cannot be seen from outside the fifty places worked in order, one message in three channels, who answers replies for 24 hours, and who may pull the launch this one is the launch, and it happens after the gate
Past launch day the gate changes shape: the post-launch runbook runs D+1 to D+90 and every stage ends in one of four decisions, keep, change the copy, change the channel or stop. Its D+1 job is that every row of the product register answers at its own address. That is the same job as the broken pages in the full crawl, one address at a time, and the crawl is the faster way to do it.