SEO report for puentedefe.com
https://puentedefe.com/ · checked Sun, 01 Nov 2026 18:14 GMT
Fix these first
- Title tagcritical
“LIGABANDOT: Cyber District Toto Slot Dengan Ekosistem Game Dan Antarmuka Dinamis”
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- XML sitemaphigh
No XML sitemap found at /sitemap.xml or in robots.txt.
Fix: Create an XML sitemap listing every page and submit it in Google Search Console.
- Broken links (sample)high
Checked 12 internal link(s).
Fix: Fix or remove links that return errors, and update links that redirect.
- Render-blocking resourceshigh
4 blocking script(s) and 4 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- HTTP → HTTPS redirecthigh
http:// does not redirect to https://.
Fix: 301-redirect all http:// requests to https://.
- LocalBusiness markuphigh
No LocalBusiness structured data.
Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.
- www / non-wwwmedium
Both www.puentedefe.com and puentedefe.com load without redirecting – Google may see duplicate sites.
Fix: Pick one version (with or without www) and 301-redirect the other to it.
- Heading structuremedium
33 headings for 306 words – a lot for the amount of text.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
Real-world speed Google PageSpeed
Loading Core Web Vitals from Google… this can take up to 30 seconds.
Authority & backlinks
Looking up which websites link to puentedefe.com…
Indexing & crawling 77%
Can search engines reach, read and index this page?
- ✓
Status codecritical
The page returned HTTP 200.
- ✓
Indexablecritical
No noindex instruction – the page can appear in search.
- ✓
robots.txthigh
robots.txt found.
Googlebot is allowed to crawl this page.
- ✗
XML sitemaphigh
No XML sitemap found at /sitemap.xml or in robots.txt.
Fix: Create an XML sitemap listing every page and submit it in Google Search Console.
- ✓
Canonical URLhigh
Canonical: https://puentedefe.com/
Points to this page (self-referencing).
- ✓
Redirectshigh
Loads directly with no redirects.
- ✗
www / non-wwwmedium
Both www.puentedefe.com and puentedefe.com load without redirecting – Google may see duplicate sites.
Fix: Pick one version (with or without www) and 301-redirect the other to it.
- !
hreflangmedium
8 hreflang link(s).
All language codes are valid.
The list doesn't include this page itself – Google requires each page to list itself.
Fix: Use valid ISO language(-region) codes, absolute URLs, include this page itself, and make sure every alternate links back.
Search snippet & sharing 46%
How the page looks in Google results and when shared.
- ✗
Title tagcritical
“LIGABANDOT: Cyber District Toto Slot Dengan Ekosistem Game Dan Antarmuka Dinamis”
About 801px of Google's ~580px desktop width – it will probably be cut off.
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- !
Meta descriptionhigh
229 characters, ~1504px of ~990px.
Long – Google will probably truncate it.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
Fix: Write a 140–155 character description that answers the searcher's question and invites the click.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="id"
Content quality 69%
Is there enough clear, useful text that matches what the page targets?
- !
Word countmedium
306 words of main content (inside <main>).
Google has no minimum word count – this is a rough guide to whether the page answers the question in full.
Fix: Add genuinely useful content: key service pages usually need 400+ words to answer what customers ask.
- i
Readabilitymedium
Reading-ease scores only work for English; this page is lang="id".
- ✓
Topic focushigh
11 of 11 title keywords appear in the main content.
- ✓
H1 headingcritical
“LIGABANDOT: Cyber District Toto Slot Dengan Ekosistem Game Dan Antarmuka Dinamis”
- ✗
Heading structuremedium
33 headings for 306 words – a lot for the amount of text.
1 skipped level(s), e.g. H2 → H4.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- ✗
Text-to-code ratiolow
2% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 63%
Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?
- ✓
AI crawler accesshigh
Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.
- ✓
Snippet controlshigh
No snippet restrictions – search and AI answers can quote this page.
- ✗
llms.txtlow
No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.
Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.
- ✗
Question-led contentmedium
No headings phrased as questions.
Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.
- ✓
Entity clarityhigh
Identified as: Organization.
3 official profile link(s) (sameAs).
- ✗
Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- !
Trust pages (E-E-A-T)medium
Links found to about and contact; missing privacy.
Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.
Structured data 100%
Machine-readable facts for rich results and AI.
- ✓
JSON-LD present & validhigh
3 JSON-LD block(s): Organization, ContactPoint, FAQPage, Question, Answer, BreadcrumbList, ListItem.
All blocks parse correctly.
- ✓
Required propertiesmedium
Key types include Google's required properties.
Google now shows FAQ rich results only for well-known government and health sites, but the markup still helps machines read your Q&As.
Links 19%
Internal linking, anchor text and broken links.
- !
Internal linkinghigh
446 internal and 11 external links.
Fix: Link to your most important pages from this page with descriptive text.
- ✗
Anchor text qualitymedium
Same text used for different pages: “gift registry”, “contact us”, “pakaian tidur”, “atasan”.
5 link(s) with no text at all.
Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.
- ✗
Broken links (sample)high
Checked 12 internal link(s).
Broken: /brand-a-z/addo.html (404), /brand-a-z/adidas.html (404), /brand-a-z/airfree.html (404), /brand-a-z/alamii.html (404), /brand-a-z/amara.html (404).
Fix: Fix or remove links that return errors, and update links that redirect.
Performance 36%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
296 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
- !
HTML sizemedium
353 kB of HTML.
Fix: Remove inline bloat, base64 images and unused markup.
- i
Compressionmedium
Couldn't be measured from our server (our fetch decodes compressed pages before we see them). Check in your browser's developer tools that HTML is sent with br or gzip.
- ✗
Render-blocking resourceshigh
4 blocking script(s) and 4 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- ✗
Scripts & third partiesmedium
206 script tag(s); files loaded from 8 other domain(s): mothercare.co.id, photopicliban.online, js.klevu.com, i.pinimg.com, platform-api.sharethis.com, maps.google.com….
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- ✗
Imagesmedium
39 image(s).
17 without width/height – can cause layout shift (CLS).
13 image(s) after the first three aren't lazy-loaded.
The first image is lazy-loaded – if it's the main (LCP) image, that delays it. Don't lazy-load images visible on arrival.
0 use WebP/AVIF or responsive srcset.
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
- ✗
Cachinglow
No Cache-Control header.
Fix: Set Cache-Control so browsers and CDNs can reuse the page.
- ✓
HTTP/3low
Server advertises HTTP/3 (faster on mobile networks).
Security 67%
Visitor safety signals that browsers and Google check.
- ✓
HTTPScritical
Secure HTTPS with no mixed content.
- ✗
HTTP → HTTPS redirecthigh
http:// does not redirect to https://.
Fix: 301-redirect all http:// requests to https://.
- ✓
HSTSmedium
HSTS: max-age=31536000
- ✗
Security headerslow
Present: none.
Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).
- ✓
Server fingerprintlow
No X-Powered-By header (server: cloudflare).
Mobile & accessibility 75%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width, initial-scale=1
- ✗
Image alt textmedium
3 of 39 images have no alt attribute.
Fix: Describe each meaningful image in its alt attribute (use alt="" for decorative ones).
- ✓
Form labelsmedium
All 3 form fields are labelled.
- ✗
Link nameslow
5 link(s) have no readable name for screen readers.
Fix: Add text or aria-label to icon-only links.
- ✓
Tap-to-contactmedium
One-tap contact: phone.
Local SEO 33%
Signals that help you appear in Google Maps and 'near me' searches.
- ✗
LocalBusiness markuphigh
No LocalBusiness structured data.
Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.
- ✓
Contact details on pagemedium
A UK phone number is shown.
No postcode found (fine for service-area businesses).
- ✗
Map & directionslow
No map or directions link.
Fix: Add a Google Maps directions link so customers can find you.