No checks match that filter.
Full diagnostics
Every check that ran, grouped by what it affects. Problems appear first in each group.
Meta Tags & Search Snippet Simulator
The tags that decide how this page is titled and described in search results.
No meta description, Google will generate a snippet from the page.
No meta description, Google will generate a snippet from the page.
Meta description
The page has no meta description, so search engines will improvise the snippet.
How to fix
The title is 16 characters. Short titles are fine, but there may be room to say more about what the page offers.
Rendered width
| Desktop | 147px | / 580px | |
| Mobile | 133px | / 920px |
Measured in Arial at the size Google renders result titles, accurate to within a fraction of a percent of a browser. Characters: 16.
Nothing in this section matches the current filter.
Crawling & indexing
Whether search engines can reach, read and index this page at all.
HTTP status
HTTP 403
The page returns HTTP 403 rather than 200.
403 https://www.lodgify.com/
How to fix
Robots directives
"noindex" is set via meta robots, so this page will not appear in search results.
meta robots: noindex,nofollow
How to fix
Robots directives
"nofollow" is set via meta robots.
meta robots: noindex,nofollow
How to fix
Canonical tag
No canonical tag, so duplicate URLs may compete with each other.
How to fix
Favicon
No favicon is declared. Google shows one beside your result on mobile.
How to fix
Missing pages (404)
HTTP 403
A page that does not exist returns HTTP 403 rather than 404, which tells search engines something other than "gone".
https://www.lodgify.com/wrp-missing-b6dddf2e06 answered HTTP 403
How to fix
The URL resolves without redirects.
Language is declared as "en-us".
lang="en-us"
No hreflang annotations, which is correct for a single-language page.
The viewport is configured for mobile.
width=device-width,initial-scale=1
The page declares UTF-8 encoding.
All resources load securely.
The URL is 24 characters.
The URL is clean and readable.
The page is 0 levels deep.
The URL has no query parameters.
robots.txt is present and does not block crawling.
A sitemap is published, listing 1768 URLs.
Lists 1768 URLs
All 3 other spellings of this address redirect here in one permanent step.
Nothing in this section matches the current filter.
Content & metadata
What the page says it is about, and how it reads.
This page has no headings.
Content length
38 words
The page has roughly 38 words, too little for search engines to tell what it is about.
How to fix
Open Graph tags
Open Graph tags are incomplete: og:title, og:description, og:image missing.
Open Graph tags
Tag Status
og:title ✕ Missing og:description ✕ Missing og:image ✕ Missing og:url ✓ Present og:type ✓ Present
How to fix
Open Graph tags
| Tag | Status | |
|---|---|---|
| og:title | ✕ | Missing |
| og:description | ✕ | Missing |
| og:image | ✕ | Missing |
| og:url | ✓ | Present |
| og:type | ✓ | Present |
Twitter card
No twitter:card tag, so shared links render as a small preview.
How to fix
Text-to-HTML ratio
0.7% text
Only 0.7% of the page is readable text; the rest is markup and script.
How to fix
The page has exactly one h1.
www.lodgify.com
The heading outline descends in order.
No data tables on this page, so there are no columns to label.
The page has too little text for keyword analysis to mean anything.
Nothing in this section matches the current filter.
AI & answer readiness
Whether answer engines and AI overviews can extract and trust this page.
Answer readiness
0 found
No heading is followed by a concise 40 to 60 word answer, the shape featured snippets and AI overviews extract.
How to fix
Content freshness
The page publishes no date. Not expected on a page like this; worth adding if its content goes out of date.
How to fix
Answer schema
No structured data an answer engine can lift directly, such as FAQPage, HowTo or Article.
How to fix
llms.txt for AI agents
No llms.txt. AI coding agents have no curated map of this site.
https://www.lodgify.com/llms.txt returned nothing
How to fix
Attribution signals present: privacy policy.
privacy policy
The page is too short to assess structure.
The page has no structured data, so there is no entity to check.
The page reads the same with and without JavaScript.
Every AI crawler checked is allowed to read this page.
Nothing in this section matches the current filter.
Speed & delivery
What makes the page slow, and what the loading experience measures.
Largest Contentful Paint
Target ≤ 2.5s
What this measures
How long until the largest thing on screen, usually the hero image, video or headline block, has finished rendering. It is a proxy for "when did this page feel loaded".
What moves it: Serve the hero image in a modern format at the size it is displayed, preload it, and remove render-blocking CSS and JavaScript ahead of it. A slow server response delays it too, so check TTFB first.
Interaction to Next Paint
Target ≤ 200ms
What this measures
How long the page takes to respond visibly after a tap, click or key press, measured across every interaction, not just the first. High INP is what makes a page feel unresponsive even once it looks ready.
What moves it: Break up long JavaScript tasks so the main thread is free to respond, defer work that is not needed for the interaction, and avoid large re-renders on every event.
Cumulative Layout Shift
Target ≤ 0.1
What this measures
How much visible content jumps around while the page loads. This is what makes someone tap the wrong thing because a banner or image pushed the layout down underneath their finger.
What moves it: Give images and video explicit width and height so the browser reserves the space, reserve room for ads and embeds, and avoid inserting content above what is already on screen.
First Contentful Paint
Target ≤ 1.8s
What this measures
How long until anything at all appears, the first text or image painted. It separates "the page starts slowly" from "the biggest element is slow": a fast FCP with a slow LCP points at the hero, while both slow points at the server.
What moves it: Cut render-blocking CSS and JavaScript in the head, inline the styles needed for the first screen, and improve the server response time.
Real-user response time
Target ≤ 800ms
What this measures
How long real visitors waited for the first byte of the response, the 75th percentile across everyone who actually loaded the page, not a single test from one location.
What moves it: Cache the response at the edge, host closer to your visitors, and reduce the work done before the first byte is sent, database queries, template rendering and third-party calls.
Page weight
257 requests · 6.2 MB
The page loads 6.2 MB in 257 requests, among the heaviest tenth of the web. On a phone connection it takes many seconds before it is usable.
What loaded, by type
Type Requests Transferred
script 107of 2 declared 3.6 MB image 61of 1 declared 1.1 MB other 74 831 KB font 8 330 KB document 3 146 KB stylesheet 2of 0 declared 112 KB media 2 36 KB
Of these, 231 requests (5.5 MB) come from third-party domains.
How to fix
What loaded, by type
| Type | Requests | Transferred | |
|---|---|---|---|
| script | 107of 2 declared | 3.6 MB | |
| image | 61of 1 declared | 1.1 MB | |
| other | 74 | 831 KB | |
| font | 8 | 330 KB | |
| document | 3 | 146 KB | |
| stylesheet | 2of 0 declared | 112 KB | |
| media | 2 | 36 KB |
Of these, 231 requests (5.5 MB) come from third-party domains.
Third-party services
33 services · 5.1 MB
33 third-party services account for 83% of what this page downloads, 5.1 MB and 3.4s of main-thread time.
Third-party services
Service Transferred Main thread
website-files.com 1.6 MB 220ms Google CDN 743 KB 433ms Google Tag Manager 728 KB 847ms tidio.co 517 KB 96ms Hubspot 321 KB 172ms Facebook 218 KB 223ms Optanon 214 KB 186ms TikTok 151 KB 138ms Crazy Egg 75 KB 92ms JSDelivr CDN 69 KB 135ms datadoghq-browser-agent.com 63 KB 110ms rudderlabs.com 52 KB 35ms
Showing the 12 heaviest of 33 services.
3.4s of main-thread time
How to fix
Third-party services
| Service | Transferred | Main thread | |
|---|---|---|---|
| website-files.com | 1.6 MB | 220ms | |
| Google CDN | 743 KB | 433ms | |
| Google Tag Manager | 728 KB | 847ms | |
| tidio.co | 517 KB | 96ms | |
| Hubspot | 321 KB | 172ms | |
| 218 KB | 223ms | ||
| Optanon | 214 KB | 186ms | |
| TikTok | 151 KB | 138ms | |
| Crazy Egg | 75 KB | 92ms | |
| JSDelivr CDN | 69 KB | 135ms | |
| datadoghq-browser-agent.com | 63 KB | 110ms | |
| rudderlabs.com | 52 KB | 35ms |
Showing the 12 heaviest of 33 services.
Browser caching
999 KB re-downloaded
81 files have cache lifetimes short enough that returning visitors download 999 KB again.
Short cache lifetimes
File Cache lifetime Size
cdn.lodgify.com/lodgify-demo.js 15d 208 KB js.hsforms.net/v2.js 5m 198 KB connect.facebook.net/1655218011431832 20m 118 KB cdn.cookielaw.org/otBannerSdk.js 1d 105 KB connect.facebook.net/fbevents.js 20m 100 KB cdn.prod.website-files.com/…b2deec6fd3132_Midjourney_Min_06%201.webp 24h 85 KB cdn.prod.website-files.com/6a0183d56ceb2deec6fd3114_3161739%201.avif 24h 73 KB cdn.prod.website-files.com/…6ceb2deec6fd3195_Stock_Min_01-p-800.avif 24h 68 KB www.datadoghq-browser-agent.com/datadog-rum.js 4h 63 KB sdk.mrf.io/marfeel-sdk.js 30m 47 KB js.hs-analytics.net/589108.js 5m 45 KB cdn.prod.website-files.com/…b2deec6fd3179_Midjourney_Max_02%201.avif 24h 42 KB
Showing the 12 largest of 81 files.
26 expire within the hour
How to fix
Short cache lifetimes
| File | Cache lifetime | Size |
|---|---|---|
| cdn.lodgify.com/lodgify-demo.js | 15d | 208 KB |
| js.hsforms.net/v2.js | 5m | 198 KB |
| connect.facebook.net/1655218011431832 | 20m | 118 KB |
| cdn.cookielaw.org/otBannerSdk.js | 1d | 105 KB |
| connect.facebook.net/fbevents.js | 20m | 100 KB |
| cdn.prod.website-files.com/…b2deec6fd3132_Midjourney_Min_06%201.webp | 24h | 85 KB |
| cdn.prod.website-files.com/6a0183d56ceb2deec6fd3114_3161739%201.avif | 24h | 73 KB |
| cdn.prod.website-files.com/…6ceb2deec6fd3195_Stock_Min_01-p-800.avif | 24h | 68 KB |
| www.datadoghq-browser-agent.com/datadog-rum.js | 4h | 63 KB |
| sdk.mrf.io/marfeel-sdk.js | 30m | 47 KB |
| js.hs-analytics.net/589108.js | 5m | 45 KB |
| cdn.prod.website-files.com/…b2deec6fd3179_Midjourney_Max_02%201.avif | 24h | 42 KB |
Showing the 12 largest of 81 files.
1 render-blocking resource in the head.
The HTML document is 5 KB.
No deprecated HTML tags are used.
3 inline style attributes.
The response is compressed with gzip.
Content-Encoding: gzip
Nothing in this section matches the current filter.
Security
Transport security, reputation and the response headers that protect visitors.
Content Security Policy
The Content-Security-Policy allows unsafe-inline or unsafe-eval, which undermines much of its protection.
default-src 'none'; script-src 'nonce-Ee9uzDwk0Z34jN6s9UiNBt' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline…
How to fix
security.txt
No security.txt, so somebody who finds a vulnerability has no published way to tell you about it.
https://www.lodgify.com/.well-known/security.txt
How to fix
No email addresses are written into the page for harvesting bots to collect.
HTTPS is enforced with Strict-Transport-Security.
max-age=15552000; includeSubDomains; preload
MIME sniffing is disabled.
The page is protected against framing.
Referrer-Policy is "same-origin".
same-origin
A Permissions-Policy limits which browser features the page and its embeds can use.
The page sets no cookies, so there are none to expose.
No software versions are disclosed in headers or the page.
The TLS certificate is valid for another 61 days, issued by "GoDaddy.com.
61 days remaining
Not listed by Google Web Risk for malware, phishing or unwanted software.
Connections use TLS 1.3.
Nothing in this section matches the current filter.
Server & domain
The server and the domain behind the page: protocol, network, registration and email records.
IPv6
www.lodgify.com has no IPv6 address. Visitors on IPv6-only mobile networks reach it through a translation gateway, which adds a step.
How to fix
Served over HTTP/2, which loads a page's files in parallel over one connection.
Served through Cloudflare, a CDN, so visitors get the page from a server near them.
lodgify.com is registered until 13 Aug 2027 with GoDaddy.com, LLC.
273 days remaining
lodgify.com was registered on 13 Aug 2012, 14 years ago. Age is not a ranking factor, but an established name is one buyers and partners look for.
lodgify.com publishes an SPF record: v=spf1 include:_spf.lodgify_com._d.easydmarc.pro ~all
lodgify.com has a DMARC policy of reject.
No ad network loads on this page, so ads.txt is not needed.
Nothing in this section matches the current filter.
Links, media & schema
Links, images and structured data.
Image dimensions
1 found
1 image has no width and height, so the page shifts as they load (hurting CLS).
# / line Image source
JS /favicon.ico<img src="/favicon.ico" class="_d93c358d7ea581c67daa8a74 _4f34305955519b32989d26da" alt="Icon for www.lodgify.com">
How to fix
| # / line | Image source |
|---|---|
| JS | /favicon.ico<img src="/favicon.ico" class="_d93c358d7ea581c67daa8a74 _4f34305955519b32989d26da" alt="Icon for www.lodgify.com"> |
Structured data
The page has no structured data, so it cannot qualify for rich results.
How to fix
0 internal and 2 external links.
0 internal, 2 external
0 internal, 2 external
Anchor text describes its destinations.
Outbound link rel attributes look appropriate.
In-page anchors resolve to real targets.
All images carry an alt attribute.
No heavy legacy image formats found.
Image loading strategy looks sound.
Images are served responsively or are small enough not to need it.
All 2 checked links resolve.
Nothing in this section matches the current filter.
What to fix first
Ranked by impact against effort, the top of this list buys the most for the least work.
Score breakdown
How each area scored. Categories that could not be measured are excluded rather than counted as zero.