This website audit report analyzes https://www.scotiabank.com.pe/Personas/Default across 12 critical dimensions with actionable recommendations.
https://www.scotiabank.com.pe/Personas/Default
48Poorout of 100
Website Audit Report
Scotiabank Perú
June 20, 2026 266ms response HTTPS Secure
Executive Summary
https://www.scotiabank.com.pe/Personas/Default scores 48/100 (F). Priority improvements needed in SEO, Performance, Security. The site has 992 words, 19 images, and 2 schema blocks. Data confidence: 90%. Sustainability score: 90/100. Focus on the top recommendations below to improve your score.
266ms
Response Time
992
Word Count
19
Images
233
Links
Website Preview
Visit SiteLoading preview…
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Title tag is very short (15 chars)
2[SEO] No H1 heading found
3[SEO] Heading hierarchy gaps: h2 → h5 (skips h3), h2 → h4 (skips h3), h2 → h4 (skips h3)
4[SEO] Missing OG tags: og:url, og:type
5[SEO] Missing Twitter tags: twitter:image
6[SEO] High link count (233) — above recommended range
7[SEO] 24 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
8[SEO] High dofollow external link count (25) — excessive link equity leakage
9[SEO] Primary keyword missing from first paragraph
10[SEO] Missing og:locale tag — social platforms may guess language/region
Top Recommendations
1[Impact: High | Effort: Low] Expand your title to 50–60 characters for better click-through rates and SERP visibility
2[Impact: High | Effort: Low] Add exactly one H1 tag with your primary keyword to establish page topic
3[Impact: High | Effort: Low] Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
4[Impact: Medium | Effort: Medium] Add missing Open Graph tags: og:url, og:type
5[Impact: Medium | Effort: Medium] Aim for ≤150–200 total links per page including nav, footer, and content links
6[Impact: Medium | Effort: Medium] Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
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 naturally in the first paragraph to establish topical relevance early
9[Impact: High | Effort: Low] Include your primary keyword in the URL slug for improved crawlability and click-through rates
10[Impact: High | Effort: Medium] Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
11[Impact: High | Effort: Medium] Link to a Contact page — essential trust signal for E-E-A-T and local SEO
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
1Meta description is 150 characters — within optimal 140–160 range (2025-2026)
2Canonical URL is set and matches the page URL
3HTML lang attribute set to "es"
4Favicon present
5205 internal links help establish site architecture
625 external links provide reference signals
7Content length of 992 words is adequate
8URL length (46 chars) is within optimal range
9No redirect chain — direct URL resolution
10Healthy internal link ratio: 88% of links are internal
11Good anchor text diversity: 77% unique anchor texts
12Primary keyword not in URL — acceptable for homepage/root URLs
13Moderate E-E-A-T signals (3 indicators)
14Table of Contents detected — improves dwell time and jump-link navigation
15Moderate entity presence: Somos Informaci, Inversionistas Personas Singular Wealth Negocios Grandes Empresas Qui, Regresa Pr
Issues Found
1Title tag is very short (15 chars)
2No H1 heading found
3Heading hierarchy gaps: h2 → h5 (skips h3), h2 → h4 (skips h3), h2 → h4 (skips h3)
4Missing OG tags: og:url, og:type
5Missing Twitter tags: twitter:image
6High link count (233) — above recommended range
724 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
8High dofollow external link count (25) — excessive link equity leakage
9Primary keyword missing from first paragraph
10Missing og:locale tag — social platforms may guess language/region
11Very high internal link density (206.7/1k words) — may appear spammy
12Low keyword density (0.2%) for "scotiabank per"
13No social sharing buttons/widgets detected
14Low OG sharing completeness (50%) — social previews will be poor
Recommendations to Reach 100%
1Expand your title to 50–60 characters for better click-through rates and SERP visibility
2Add exactly one H1 tag with your primary keyword to establish page topic
3Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
4Add missing Open Graph tags: og:url, og:type
5Aim for ≤150–200 total links per page including nav, footer, and content links
6Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
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 naturally in the first paragraph to establish topical relevance early
9Include your primary keyword in the URL slug for improved crawlability and click-through rates
10Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
11Link to a Contact page — essential trust signal for E-E-A-T and local SEO
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
16Upgrade Twitter card to "summary_large_image" for larger, more engaging previews
17Reduce internal link density — excessive linking dilutes individual link value
18Increase primary keyword usage to 0.5–2.5% density — include it naturally in headings, paragraphs, and image alt text
19Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
20Add social share buttons (Facebook, Twitter/X, LinkedIn, WhatsApp) to encourage content distribution and earn social signals
21Complete your Open Graph tags (og:title, og:description, og:image, og:url, og:type, og:locale) for rich social media previews
Key Findings
1Excellent server response time: 266ms
2HTML size is 141KB — acceptable
3Preloaded resources: style, style, style, style
40 async and 1 deferred scripts
5Cache-Control header with max-age is set
6Gzip compression enabled
7Estimated INP: ~166ms — within Google's "good" threshold (<200ms)
8Comprehensive analytics: GA4 (G-04YV5QR77N) + GTM (GTM-KMZP7R) with event tracking
Issues Found
111 render-blocking scripts slow down initial paint
2No lazy loading on images
3No WebP or AVIF image formats found
4No responsive image srcset found
5Only 0/19 images have width/height attributes
6No font-display property found
722 inline <style> blocks
816 inline scripts
9Moderate CSS payload (~348KB)
10Moderate JavaScript payload (~675KB)
11233 links increase DOM size and parsing time
12HTTP/1.1 detected — no multiplexing
13No CDN detected
149 third-party scripts detected
1510 render-blocking CSS files — delays first paint
16Estimated CSS bundle ~458KB — above optimal
17Estimated LCP: ~2566ms — needs improvement (goal: <2.5s)
18Moderate estimated CLS: 0.25 — above 0.1 "good" threshold
Recommendations to Reach 100%
1Convert all non-critical scripts to async/defer to eliminate render-blocking resources
2Add loading="lazy" to below-the-fold images to improve initial page load
3Convert images to WebP or AVIF format for 30–50% file size reduction
4Use srcset and sizes attributes on images to serve appropriately sized images per device
5Add explicit width and height to all images to prevent Cumulative Layout Shift (CLS)
6Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
7Add font-display: swap to web font declarations to show fallback text while fonts load
8Extract inline styles into external CSS files for better caching and maintainability
9Move inline scripts to external files with defer attributes
10Consider purging unused CSS and using critical CSS extraction to reduce render-blocking stylesheets
11Optimize JavaScript delivery with code splitting, deferred loading, and removing duplicate modules
12Reduce links per page to improve DOM parsing performance and reduce memory usage
13Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
14Use a Content Delivery Network (CDN) like Cloudflare, CloudFront, or Fastly to reduce global latency
15Review third-party scripts and defer non-essential ones to improve page load time
16Reduce render-blocking CSS by inlining critical CSS, using media queries on non-critical stylesheets, and loading non-critical CSS asynchronously
17Reduce CSS bundle size with PurgeCSS/tree-shaking. Aim for <200KB total CSS
18Optimize Largest Contentful Paint: preload hero image, reduce render-blocking resources, use CDN for static assets
19Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
Key Findings
1Viewport meta tag present: width=device-width, initial-scale=1
2HTML5 doctype declared
3Apple touch icons present
Issues Found
1Missing charset declaration
2No theme-color meta tag
3No web app manifest found
4No responsive image srcset — mobile users may download oversized images
5Popup/modal/interstitial detected — Google penalizes intrusive interstitials on mobile
6Only 3 manifest icon size(s) — recommend at least 4 (192, 384, 512, maskable)
Recommendations to Reach 100%
1Add <meta charset="UTF-8"> in the <head>
2Add <meta name="theme-color"> for browser chrome styling on mobile
3Create a manifest.json for PWA capabilities and add-to-homescreen support
4Consider implementing a service worker for offline support and faster repeat visits
5Implement srcset to serve smaller images on mobile devices, saving bandwidth
6Remove or minimize intrusive interstitials on mobile — Google's Page Experience update penalizes full-screen popups that block content
7Add multiple icon sizes (192x192, 384x384, 512x512, plus maskable) to your manifest for cross-device support
8Add env(safe-area-inset-*) CSS for proper display on notched/island devices
9Add :active / touch-action CSS for tactile feedback on mobile interactions
Key Findings
1HTTPS enabled — encrypted connection
2HSTS header present — enforces HTTPS
3Content Security Policy header present
4X-Content-Type-Options: nosniff is set
5X-Frame-Options header prevents clickjacking
6Referrer-Policy set to: no-referrer-when-downgrade
7Server header not exposing technology details
8Privacy policy link detected
9Subresource Integrity (SRI) on 21 resource(s) — prevents CDN tampering
10jQuery 3.7.1 — current version
11Rate limiting recommended for form endpoints
Issues Found
1Missing Permissions-Policy header
224 external links missing rel="noopener noreferrer" — security risk
3HSTS header present but missing preload directive
4Cookie security issues: missing Secure flag; missing HttpOnly flag; missing SameSite attribute
5No cookie consent banner detected
6Weak CSP implementation (strictness score: 25/100)
7CSP contains 3 unsafe-inline directive(s) — weakens XSS protection
Recommendations to Reach 100%
1Add Permissions-Policy to restrict access to camera, microphone, geolocation, etc.
2Add Cross-Origin-Opener-Policy: same-origin-allow-popups
3Add Cross-Origin-Resource-Policy: cross-origin
4Add rel="noopener noreferrer" to all external links with target="_blank" to prevent tabnabbing attacks
5Add "preload" to your HSTS header and submit to hstspreload.org for maximum HTTPS enforcement
6Set Secure, HttpOnly, and SameSite=Strict (or Lax) attributes on all cookies to prevent session hijacking and CSRF
7Implement a cookie consent banner for GDPR/ePrivacy compliance
8Significantly strengthen CSP: eliminate unsafe-inline and unsafe-eval, use nonce-based policies, define explicit source lists per directive (OWASP Level 3)
9Replace unsafe-inline with nonce-based CSP or hash-based allowlisting for inline scripts/styles
10Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
Key Findings
1Language declared: es
2All key landmarks present (main, nav, footer)
3All 19 images have alt attributes
4Rich ARIA implementation: 15 elements with ARIA attributes
5Focus styles detected for keyboard navigation
Issues Found
1No skip navigation link
22 form(s) missing proper labels
31 button(s) missing accessible labels
4Heading hierarchy has gaps — confusing for screen readers
54 minor HTML validity issue(s)
619 images missing explicit dimensions — causes layout shifts for screen reader users
71 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 <label> elements associated with every form input via for/id attributes
3Add text content or aria-label to all buttons
4Review and fix HTML structure issues for better accessibility and cross-browser compatibility
5Set explicit width and height (or CSS aspect-ratio) on all images to prevent layout shifts that disorient assistive technology users
6Ensure all element IDs are unique — duplicate IDs break form labels, ARIA relationships, and fragment navigation
Key Findings
12 schema block(s): Organization
2Strong semantic markup: section, header, nav, main, article, footer
3Complete social metadata (OG + Twitter Card)
4FAQ/Q&A content patterns detected — highly valuable for AI citation
518 strong entity mentions (bold/emphasized text)
6Social presence signals: facebook, twitter, youtube, linkedin, instagram
7No AI crawlers blocked via meta tags — content accessible to AI search engines
8robots.txt file found
9High RAG-friendliness (100/100): 0 headings with IDs, 18 section anchors
10Content provenance signals detected (citations with sources, attributed claims)
11Good HTML-to-text ratio (31%) — AI crawlers can extract content efficiently
Issues Found
1No breadcrumb navigation
2No sitemap reference found
3robots.txt has no Sitemap directive
4No llms.txt file found — AI models cannot find structured guidance for your site
5No content freshness signals (dateModified, datePublished, <time> elements)
Recommendations to Reach 100%
1Add more structured data types (FAQ, HowTo, Breadcrumb) to improve AI comprehension
2Add hreflang tags if your site serves multiple languages or regions
3Add breadcrumb navigation with BreadcrumbList schema for better site hierarchy signals
4Create and reference an XML sitemap for AI crawler discoverability
5Add a Sitemap: directive to your robots.txt pointing to your XML sitemap for AI and search crawler discoverability
6Create /llms.txt following the llms.txt standard: # Title, > description, ## Overview, ## Core Services, ## Key Pages with full URLs
7Create /llms-full.txt with comprehensive documentation (services, pricing, team, case studies) for AI models that need depth
8Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your HTML <head> for AI discoverability
9Add dateModified and datePublished meta tags and use <time datetime="..."> elements — AI models prefer fresh, timestamped content
Key Findings
1Moderate content depth (992 words)
2Strong entity emphasis: 18 key terms highlighted
3Good semantic-to-div ratio: 70 semantic elements
4Structured content: 44 lists, 0 tables — easily parsed by AI
520 external citations — strong reference density for AI model training
6Trust signals present: Trust Badges, HTTPS Security
7Clear value proposition detected in heading elements
Issues Found
1No structured Q&A content
2Weak E-E-A-T schema signals
3No author or expertise signals
4No clear call-to-action elements detected
5No CTA above the fold
6No social proof elements
Recommendations to Reach 100%
1Add FAQ or Q&A sections — AI models heavily rely on question-answer patterns for training data
2Add Person, Article, and Review schemas to demonstrate expertise, experience, authoritativeness, and trustworthiness
3Add Speakable schema markup to help voice assistants identify the most important content
4Include expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
5Add visible author bylines with bios and link to author pages — AI models evaluate content credibility through authorship signals
6Add prominent CTAs with action-oriented text ("Get Started", "Book a Call", "Try Free") — every page should guide users toward conversion
7Place a clear CTA in your hero/header section so visitors see a conversion path immediately upon landing
8Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
Key Findings
1Direct question-answer patterns found — good for Google SGE and AI citations
244 lists provide scannable, AI-friendly content
318 emphasized terms suggest unique, quotable insights
42 schema blocks help AI engines understand content context
Issues Found
1No data tables for AI comparison extraction
2No hreflang tags — generative engines cannot determine language/region targeting
Recommendations to Reach 100%
1Add comparison tables with structured data — generative AI engines frequently cite tabular content
2Include how-to or step-by-step instructional content for generative AI answer inclusion
3Consider using <dl>/<dt>/<dd> definition lists for key terms and concepts
4Add bidirectional hreflang tags with x-default to help AI engines serve the correct language variant
5Add original data visualizations, charts, or data tables — generative engines cite pages with unique, first-party data
6Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
Key Findings
1Question-answer heading patterns support featured snippet capture
244 lists provide scannable answers for People Also Ask
310 concise answer-length paragraphs (10–50 words) — ideal for snippet extraction
Issues Found
1No FAQ content or schema
2No Speakable schema for voice search
3No breadcrumb navigation
4No direct answer patterns ("X is defined as...", "X refers to...")
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
3Add Speakable schema to mark sections suitable for text-to-speech by voice assistants
4Add breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals
5Consider adding video content with VideoObject schema for multimedia search results
6Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
Key Findings
1NAP information detected: phone: 2021010719
2Phone number(s) visible: 2021010719, 4299481
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%
1Consider displaying a business email for direct contact signals
2Add LocalBusiness (or specific subtype like ProfessionalService) JSON-LD schema with name, address, phone, hours, and geo coordinates
3Add an embedded Google Map to your contact or about page for local search signals
4Add PostalAddress schema or itemprop="address" microdata to your address elements
5Add geo.region, geo.placename, and geo.position meta tags for geographic targeting
6Add AggregateRating schema to display star ratings in search results — reviews significantly impact local click-through rates
Key Findings
12 JSON-LD block(s) with types: Organization
2All structured data uses JSON-LD format — Google's recommended format
3Moderate schema coverage
4Some top-tier schemas: Organization
5Entity linking via sameAs: 5 external profiles linked — strengthens Knowledge Graph
Issues Found
1Invalid JSON-LD block detected
2Schema property completeness averaging 57%
3No rich results eligibility detected
Recommendations to Reach 100%
1Add more top-tier schema types — consider: LocalBusiness, Product, Article
2Consider adding secondary schema types: Person, HowTo, Service, Event for richer search features
3Add missing high-impact schemas: WebSite
4Add BreadcrumbList schema — enables breadcrumb rich results in Google
5Add FAQPage schema to FAQ content — enables expandable rich results
6Consider adding HowTo schema for instructional content
7Fix invalid JSON-LD blocks — validate at schema.org/validator or Google Rich Results Test
8Add more schema types — diverse structured data improves AI and search engine understanding
9Fill in missing recommended properties for each schema type
10Add FAQ, HowTo, or Breadcrumb schema to become eligible for enhanced search result features
11Add nested schemas (e.g., author within Article, offers within Product) to define entity relationships
12Add SearchAction schema to your WebSite type to enable the sitelinks search box in Google results
Key Findings
1Links are visually distinguishable (underline or decoration detected)
2Relative units (rem/em/clamp) detected — supports text resizing
3Good semantic element usage (70 semantic elements)
4Focus styles detected for keyboard navigation visibility
5Page language declared — aids assistive technology
6All ARIA roles are valid
7Focus not obscured by sticky/fixed elements (WCAG 2.4.11)
8Accessible authentication detected (autocomplete, no CAPTCHA barriers) — WCAG 3.3.8
Issues Found
1No prefers-reduced-motion support
2No high contrast mode support
3No error suggestion mechanisms detected in forms
431 elements with tabindex="-1" — may hide content from keyboard users
53 heading level skip(s) — confuses screen reader navigation
6No form error identification detected
Recommendations to Reach 100%
1Add @media (prefers-reduced-motion: reduce) to disable animations for users who are sensitive to motion
2Add @media (prefers-contrast: high) or (forced-colors: active) styles for users with low vision
3Add aria-invalid, aria-errormessage, and visible error messages for form validation (WCAG 3.3.3)
4Review elements with tabindex="-1" — ensure important interactive elements remain keyboard-accessible
5Use sequential heading levels (H1→H2→H3) without skipping — screen reader users navigate by heading hierarchy (WCAG 1.3.1)
6Add aria-invalid, aria-errormessage, and inline error messages to form fields (WCAG 3.3.1/3.3.3)
7Add aria-live regions (role="status" or role="alert") for form feedback, notifications, and dynamic content updates (WCAG 4.1.3)
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.