This website audit report analyzes https://larepublica.pe/ across 12 critical dimensions with actionable recommendations.
https://larepublica.pe/
53Needs Workout of 100
Website Audit Report
Últimas noticias del Perú y el Mundo | La República
August 1, 2026 146ms response HTTPS Secure
Executive Summary
https://larepublica.pe/ scores 53/100 (F). Priority improvements needed in SEO, Security, AI Readiness. The site has 1953 words, 200 images, and 4 schema blocks. Data confidence: 90%. Sustainability score: 60/100. Focus on the top recommendations below to improve your score.
146ms
Response Time
1,953
Word Count
200
Images
293
Links
Website Preview
Visit SiteLoading preview…
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Meta description is short (105 chars)
2[SEO] Heading hierarchy gaps: h2 → h4 (skips h3)
3[SEO] Missing Twitter tags: twitter:image
4[SEO] High link count (293) — above recommended range
5[SEO] 17 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
6[SEO] Title and description are identical to Open Graph tags — missed optimization opportunity
7[SEO] Title and H1 share no keywords — misaligned topic signals
8[SEO] High dofollow external link count (30) — excessive link equity leakage
9[SEO] Primary keyword "ltimas noticias del" not found in H1
10[SEO] Primary keyword missing from first paragraph
Top Recommendations
1[Impact: High | Effort: Low] Expand your meta description to 140–160 characters for better SERP visibility
2[Impact: High | Effort: Low] Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
3[Impact: Medium | Effort: Medium] Aim for ≤150–200 total links per page including nav, footer, and content links
4[Impact: Medium | Effort: Medium] Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
5[Impact: High | Effort: Low] Customize og:title and og:description separately from page title/meta description for better social sharing CTR
6[Impact: High | Effort: Low] Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
7[Impact: Medium | Effort: Low] Reduce dofollow external links to 2–5 per page. Add rel="nofollow" to low-value or affiliate links to preserve PageRank
8[Impact: High | Effort: Low] Include your primary keyword in the H1 heading for strongest on-page SEO signal
9[Impact: High | Effort: Low] Include your primary keyword naturally in the first paragraph to establish topical relevance early
10[Impact: High | Effort: Low] Include your primary keyword in the URL slug for improved crawlability and click-through rates
11[Impact: High | Effort: Medium] Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
12[Impact: Medium | Effort: Low] Add <meta property="og:locale" content="en_US"> (or your locale) for precise language targeting in social shares
Detailed Category Analysis
Key Findings
1Title tag is 51 characters — within optimal 50–60 range (Google 2025-2026)
2Single H1 tag present: "Ollanta Humala sale de Barbadillo tras resolución del TC"
3Canonical URL is set and matches the page URL
4Complete Open Graph tags (title, description, image, url, type)
5HTML lang attribute set to "es"
6Favicon present
7264 internal links help establish site architecture
829 external links provide reference signals
9Content length of 1953 words is adequate
10URL length (23 chars) is within optimal range
11No redirect chain — direct URL resolution
12SPA framework detected (nextjs) with adequate SSR content
13Healthy internal link ratio: 90% of links are internal
14Good anchor text diversity: 78% unique anchor texts
15Primary keyword not in URL — acceptable for homepage/root URLs
16Moderate E-E-A-T signals (4 indicators)
17OG image dimensions ≥1200×630px — optimal for all platforms
18Twitter card uses summary_large_image — maximum visual impact
19Moderate entity presence: El Ni, Keiko Fujimori, Sandy Carri
20Social share buttons detected: ShareThis
Issues Found
1Meta description is short (105 chars)
2Heading hierarchy gaps: h2 → h4 (skips h3)
3Missing Twitter tags: twitter:image
4High link count (293) — above recommended range
517 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
6Title and description are identical to Open Graph tags — missed optimization opportunity
7Title and H1 share no keywords — misaligned topic signals
8High dofollow external link count (30) — excessive link equity leakage
9Primary keyword "ltimas noticias del" not found in H1
10Primary keyword missing from first paragraph
11Missing og:locale tag — social platforms may guess language/region
12Very high internal link density (135.2/1k words) — may appear spammy
13Primary keyword "ltimas noticias del" not found in body content
14Long content without Table of Contents
Recommendations to Reach 100%
1Expand your meta description to 140–160 characters for better SERP visibility
2Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
3Aim for ≤150–200 total links per page including nav, footer, and content links
4Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
5Customize og:title and og:description separately from page title/meta description for better social sharing CTR
6Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
7Reduce dofollow external links to 2–5 per page. Add rel="nofollow" to low-value or affiliate links to preserve PageRank
8Include your primary keyword in the H1 heading for strongest on-page SEO signal
9Include your primary keyword naturally in the first paragraph to establish topical relevance early
10Include your primary keyword in the URL slug for improved crawlability and click-through rates
11Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
12Add <meta property="og:locale" content="en_US"> (or your locale) for precise language targeting in social shares
13Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
14Add <meta property="article:published_time"> for content freshness signals in social shares
15Add <meta property="article:modified_time"> to signal content freshness
16Reduce internal link density — excessive linking dilutes individual link value
17Include your primary keyword naturally throughout the content body — aim for 0.5–2.5% density
18Add a Table of Contents with anchor links for articles over 1500 words — improves UX, dwell time, and enables jump-link rich results
19Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
20OG sharing completeness at 83% — add missing tags for better social previews
Key Findings
1Excellent server response time: 146ms
2HTML is 1409KB — typical for SSR framework with rich content
3No render-blocking scripts detected
4189/200 images use lazy loading
5Modern image formats (WebP/AVIF) detected
6Responsive images with srcset detected
7Most images have explicit width/height attributes (prevents layout shift)
8Preconnect hints for: https://imgmedia.larepublica.pe, https://fonts.gstatic.com, https://www.googletagmanager.com
9Preloaded resources: font, font, style, style
102 async and 13 deferred scripts
11Cache-Control header with max-age is set
1223 inline scripts (framework hydration/data — standard for SSR apps)
13Lean CSS payload (~101KB)
14JavaScript payload (~1747KB) is acceptable for framework app
15HTTP/3 (QUIC) detected — fastest connection protocol
16CDN detected: CloudFront — reduces latency for global users
17Gzip compression enabled
181 third-party script(s) — manageable count
197 resource hints (preconnect/prefetch/preload) optimize loading
202 font(s) preloaded for faster text rendering
212 framework hydration script(s) — standard for SSR apps
22Estimated LCP: ~706ms — within Google's "good" threshold (<2.5s)
23Estimated INP: ~290ms — acceptable for framework-hydrated app
Issues Found
1No font-display property found
218 inline <style> blocks
3293 links increase DOM size and parsing time
4Moderate estimated CLS: 0.25 — above 0.1 "good" threshold
5Basic analytics only — missing event tracking or tag management
Recommendations to Reach 100%
1Add font-display: swap to web font declarations to show fallback text while fonts load
2Extract inline styles into external CSS files for better caching and maintainability
3Reduce links per page to improve DOM parsing performance and reduce memory usage
4Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
5Improve INP: break up long JavaScript tasks, use web workers for heavy computation, debounce input handlers
6Upgrade analytics: add Google Tag Manager for flexible tag deployment and configure custom events (form submissions, CTA clicks, scroll depth)
Key Findings
1Viewport meta tag present: width=device-width
2HTML5 doctype declared
3Character encoding declared
4Theme color meta tag set for mobile browsers
5Apple touch icons present
6Responsive images via srcset serve appropriate sizes per device
7189 images with lazy loading benefit mobile data users
Issues Found
1No web app manifest found
2Popup/modal/interstitial detected — Google penalizes intrusive interstitials on mobile
3Only 3 manifest icon size(s) — recommend at least 4 (192, 384, 512, maskable)
4Estimated page weight ~13407KB — heavy for mobile data plans
Recommendations to Reach 100%
1Create a manifest.json for PWA capabilities and add-to-homescreen support
2Consider implementing a service worker for offline support and faster repeat visits
3Remove or minimize intrusive interstitials on mobile — Google's Page Experience update penalizes full-screen popups that block content
4Add multiple icon sizes (192x192, 384x384, 512x512, plus maskable) to your manifest for cross-device support
5Add env(safe-area-inset-*) CSS for proper display on notched/island devices
6Add :active / touch-action CSS for tactile feedback on mobile interactions
7Reduce page weight below 3MB: optimize images (WebP/AVIF), defer non-critical JS, remove unused CSS
Key Findings
1HTTPS enabled — encrypted connection
2Server header not exposing technology details
3No cookie security issues detected
4Rate limiting recommended for form endpoints
5No server software/technology fingerprints exposed in headers or markup
6No stack traces or sensitive error details exposed in responses
7No obvious secret/API-key patterns exposed in page source
8Client-side library inventory (SBOM): React
913 script resource(s) catalogued for software-composition review
10No common sensitive paths (.git, .env, server-status, …) were publicly accessible
Issues Found
1Missing Strict-Transport-Security header
2Missing Content-Security-Policy header
3Missing X-Content-Type-Options header
4Missing X-Frame-Options header
5Missing Referrer-Policy header
6Missing Permissions-Policy header
717 external links missing rel="noopener noreferrer" — security risk
8No privacy policy detected
9No cookie consent banner detected
10No Subresource Integrity (SRI) on external scripts
11security.txt file is missing — no standardized channel for reporting vulnerabilities
1220 email address(es) exposed in page source (e.g. [email protected], [email protected]) — can be harvested for spam/phishing
13A private/internal IP address (RFC 1918) is disclosed in the page source — reveals internal network topology
141 untrusted <iframe>(s) without a sandbox attribute — embedded content runs with full privileges
Recommendations to Reach 100%
1Add Strict-Transport-Security header with max-age=63072000; includeSubDomains; preload
2Implement a Content Security Policy to prevent XSS and injection attacks
3Add X-Content-Type-Options: nosniff to prevent MIME type sniffing
4Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking attacks
5Add Referrer-Policy: strict-origin-when-cross-origin to control referrer leakage
6Add Permissions-Policy to restrict access to camera, microphone, geolocation, etc.
7Add Cross-Origin-Opener-Policy: same-origin-allow-popups
8Add Cross-Origin-Resource-Policy: cross-origin
9Add rel="noopener noreferrer" to all external links with target="_blank" to prevent tabnabbing attacks
10Add a privacy policy link — required by GDPR, CCPA, and builds user trust
11Implement a cookie consent banner for GDPR/ePrivacy compliance
12Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks
13Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
14Add an RFC 9116 security.txt at /.well-known/security.txt with Contact and Expires fields so researchers can responsibly report security issues [Impact: Low | Effort: Low]
15If these emails are not meant to be public, obfuscate them or replace with a contact form; for intentional contact addresses this is informational only [Impact: Info | Effort: Low]
16Remove references to internal hostnames/IP addresses from public responses [Impact: Medium | Effort: Low]
17Add the sandbox attribute (with the minimum required allow-* tokens) to iframes embedding third-party/untrusted content [Impact: Medium | Effort: Low]
Key Findings
1Language declared: es
2Rich ARIA implementation: 18 elements with ARIA attributes
Issues Found
1No skip navigation link
2Missing landmarks: main, nav, footer
317 of 200 images (9%) missing alt text
43 form(s) missing proper labels
51 iframe(s) missing title
61 button(s) missing accessible labels
7Heading hierarchy has gaps — confusing for screen readers
8No focus styles detected
97 HTML validity issues detected — affects assistive technology parsing
102 button(s) with no accessible label
111 duplicate ID(s) — breaks ARIA references and label associations
Recommendations to Reach 100%
1Add a "Skip to main content" link as the first focusable element for keyboard users
2Add semantic landmark elements: <main>, <nav>, <footer>
3Add descriptive alt text to all images — use empty alt="" only for decorative images
4Add <label> elements associated with every form input via for/id attributes
5Add descriptive title attributes to all iframes
6Add text content or aria-label to all buttons
7Add :focus-visible styles to all interactive elements for keyboard navigation visibility
8Fix HTML nesting errors and deprecated elements. Validate at validator.w3.org for WCAG compliance
9Add text content, aria-label, or title to all buttons — icon-only buttons need aria-label (WCAG 4.1.2)
10Ensure all element IDs are unique — duplicate IDs break form labels, ARIA relationships, and fragment navigation
Key Findings
1Rich structured data: 4 schema blocks (NewsMediaOrganization, Organization, WebSite, ItemList)
2Strong semantic markup: aside, header, figure, figcaption, section, article
3Complete social metadata (OG + Twitter Card)
4Social presence signals: youtube, facebook, twitter, instagram, tiktok
5No AI crawlers blocked via meta tags — content accessible to AI search engines
6High RAG-friendliness (100/100): 0 headings with IDs, 23 section anchors
7Content provenance signals detected (citations with sources, attributed claims)
8JS content ratio 78% — expected for SSR framework apps that serve pre-rendered HTML with hydration scripts
Issues Found
1No breadcrumb navigation
2No FAQ or Q&A content patterns found
3No sitemap reference found
4No robots.txt file found
5No llms.txt file found — AI models cannot find structured guidance for your site
6No content freshness signals (dateModified, datePublished, <time> elements)
Recommendations to Reach 100%
1Add hreflang tags if your site serves multiple languages or regions
2Add breadcrumb navigation with BreadcrumbList schema for better site hierarchy signals
3Add an FAQ section with FAQPage schema to increase chances of AI engine citations
4Create and reference an XML sitemap for AI crawler discoverability
5Use <strong> and <em> tags to highlight key entities, concepts, and terms
6Create a robots.txt file at your domain root — essential for crawler governance and AI SEO strategy
7Create /llms.txt following the llms.txt standard: # Title, > description, ## Overview, ## Core Services, ## Key Pages with full URLs
8Create /llms-full.txt with comprehensive documentation (services, pricing, team, case studies) for AI models that need depth
9Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your HTML <head> for AI discoverability
10Add dateModified and datePublished meta tags and use <time datetime="..."> elements — AI models prefer fresh, timestamped content
Key Findings
1Comprehensive content (1953 words) — strong for AI model training
2Good semantic-to-div ratio: 153 semantic elements
3Structured content: 7 lists, 0 tables — easily parsed by AI
415 external citations — strong reference density for AI model training
5Author attribution present but missing expertise signals
6Trust signals present: Trust Badges, HTTPS Security
7Clear value proposition detected in heading elements
Issues Found
1No structured Q&A content
2Weak entity markup — few terms emphasized
3Weak E-E-A-T schema signals
4Paragraphs are too long for optimal AI consumption
5No clear call-to-action elements detected
6No CTA above the fold
7No social proof elements
Recommendations to Reach 100%
1Add FAQ or Q&A sections — AI models heavily rely on question-answer patterns for training data
2Use <strong>, <em>, and <mark> to highlight key entities, concepts, and brand terms for AI comprehension
3Add Person, Article, and Review schemas to demonstrate expertise, experience, authoritativeness, and trustworthiness
4Break long paragraphs into shorter ones (under 30 words) for better AI comprehension and snippet extraction
5Add Speakable schema markup to help voice assistants identify the most important content
6Include expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
7Add author bio, credentials, and links to establish expertise signals for AI E-E-A-T evaluation
8Add prominent CTAs with action-oriented text ("Get Started", "Book a Call", "Try Free") — every page should guide users toward conversion
9Place a clear CTA in your hero/header section so visitors see a conversion path immediately upon landing
10Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
Key Findings
17 lists provide scannable, AI-friendly content
2Comprehensive content depth (1953 words) supports AI citation
34 schema blocks help AI engines understand content context
476 original data elements (charts, figures, data tables)
Issues Found
1No direct Q&A patterns for generative AI extraction
2No data tables for AI comparison extraction
3paragraphs may be too long for featured snippets
4No hreflang tags — generative engines cannot determine language/region targeting
Recommendations to Reach 100%
1Structure content with clear questions as headings (H2/H3) followed by concise, definitive answers in the first paragraph
2Add comparison tables with structured data — generative AI engines frequently cite tabular content
3Include how-to or step-by-step instructional content for generative AI answer inclusion
4Consider using <dl>/<dt>/<dd> definition lists for key terms and concepts
5Include unique statistics, expert quotes, and original insights that generative AI would want to cite
6Add bidirectional hreflang tags with x-default to help AI engines serve the correct language variant
7Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
Key Findings
17 lists provide scannable answers for People Also Ask
Issues Found
1No FAQ content or schema
2Content not optimized for featured snippets
3No Speakable schema for voice search
4Paragraphs too long for answer engine extraction
5No breadcrumb navigation
6Few concise answer paragraphs for snippet extraction
7No direct answer patterns ("X is defined as...", "X refers to...")
8Paragraphs too long for voice assistant extraction
Recommendations to Reach 100%
1Create an FAQ section with FAQPage structured data — essential for People Also Ask and featured snippet inclusion
2Consider adding how-to content with HowTo schema for step-by-step rich results
3Use question-based H2/H3 headings followed by a direct 40–60 word answer paragraph for featured snippet targeting
4Add Speakable schema to mark sections suitable for text-to-speech by voice assistants
5Keep answer paragraphs under 30 words — voice assistants and answer engines prefer concise, direct responses
6Add breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals
7Consider adding video content with VideoObject schema for multimedia search results
8Write concise 40–60 word paragraphs that directly answer common questions — these are extracted as featured snippets and voice answers
9Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
10Keep paragraphs under 30 words for voice search — voice assistants read concise, conversational content
Key Findings
1NAP information detected: phone: 4226215, email: [email protected]
2Phone number(s) visible: 4226215, 2205660
3Email address found: [email protected]
Issues Found
1No LocalBusiness structured data
2No Google Maps embed
3No address microdata
4No geo meta tags
5No review/rating schema
Recommendations to Reach 100%
1Add LocalBusiness (or specific subtype like ProfessionalService) JSON-LD schema with name, address, phone, hours, and geo coordinates
2Add an embedded Google Map to your contact or about page for local search signals
3Add PostalAddress schema or itemprop="address" microdata to your address elements
4Add geo.region, geo.placename, and geo.position meta tags for geographic targeting
5Add AggregateRating schema to display star ratings in search results — reviews significantly impact local click-through rates
Key Findings
14 JSON-LD block(s) with types: NewsMediaOrganization, Organization, WebSite, ItemList
2Some microdata attributes detected alongside JSON-LD — common for address/local business markup in modern frameworks
3Comprehensive schema implementation
4Some top-tier schemas: Organization, WebSite
5Rich schema diversity: 4 distinct types with properties
6Entity linking via sameAs: 4 external profiles linked — strengthens Knowledge Graph
7Average schema property completeness: 81% — well-implemented
8SearchAction schema present — eligible for sitelinks search box in Google
Issues Found
1ItemList has very few properties (2)
2No rich results eligibility detected
Recommendations to Reach 100%
1When feasible, consolidate all structured data into JSON-LD format
2Add more top-tier schema types — consider: LocalBusiness, Product, Article
3Consider adding secondary schema types: Person, HowTo, Service, Event for richer search features
4Add missing high-impact schemas: Article, Person
5Add BreadcrumbList schema — enables breadcrumb rich results in Google
6Add FAQPage schema to FAQ content — enables expandable rich results
7Consider adding HowTo schema for instructional content
8Add more properties to schema types — aim for at least 5 meaningful properties per type
9Add FAQ, HowTo, or Breadcrumb schema to become eligible for enhanced search result features
Key Findings
1prefers-reduced-motion support detected — respects user motion preferences
2High contrast / forced-colors mode supported
3Links are visually distinguishable (underline or decoration detected)
4Relative units (rem/em/clamp) detected — supports text resizing
5Good semantic element usage (153 semantic elements)
6Page language declared — aids assistive technology
7All ARIA roles are valid
8Focus not obscured by sticky/fixed elements (WCAG 2.4.11)
9Accessible authentication detected (autocomplete, no CAPTCHA barriers) — WCAG 3.3.8
10prefers-reduced-motion detected but enforcement unclear
Issues Found
1No error suggestion mechanisms detected in forms
2No focus styles detected
3No form error identification detected
Recommendations to Reach 100%
1Add aria-invalid, aria-errormessage, and visible error messages for form validation (WCAG 3.3.3)
2Add :focus-visible CSS styles to all interactive elements (WCAG 2.4.7)
3Add aria-invalid, aria-errormessage, and inline error messages to form fields (WCAG 3.3.1/3.3.3)
4Add aria-live regions (role="status" or role="alert") for form feedback, notifications, and dynamic content updates (WCAG 4.1.3)
5Ensure prefers-reduced-motion actually disables animations (set animation: none and transition: none in the media query)
Limited-Time Offer
All 12 Optimizations — Bundled Into Your Custom Website
We're currently bundling every optimization from this audit — SEO, AIO, GEO, AEO, Schema.org, WCAG accessibility, performance, security, and more — directly into our Custom Web Application Development service.
Instead of fixing issues after launch, we eliminate them from the start. Every website we build ships production-ready with a 90+ score across all 12 audit dimensions.