Recursos · 06
Web segura y de alto rendimiento: una guía de auditoría basada en el recorrido
Audite la velocidad, accesibilidad, seguridad y conversión en torno a las acciones que los usuarios realmente necesitan completar.
Actualizado · 9 min
Lo que esta guía ayuda a lograr
- Priorizar bloqueadores de usuarios reales
- Reducir peso, dependencias y superficie de ataque
- Conectar rendimiento a conversión
- Validar correcciones en condiciones realistas
Comprobación rápida
- ¿Se nombran los tres recorridos más valiosos?
- ¿Los datos de campo están segmentados para móviles?
- ¿Se puede utilizar el sitio mediante teclado?
- ¿Todos los scripts de terceros tienen un propietario?
- ¿Los errores de formulario ayudan a los usuarios a finalizar la acción?
Método paso a paso
- 1
Elige recorridos críticos
Seleccionar búsqueda, lectura, contacto, registro, compra o administración en función del valor del negocio. Describa el dispositivo, la red, el contexto y el resultado esperado.
Entregable: escenarios de prueba priorizados.
- 2
Medida de campo y laboratorio
Combina datos agregados de usuarios reales con pruebas reproducibles. Observe la carga, la capacidad de respuesta, la estabilidad, los errores y el abandono sin reducir el análisis a una puntuación.
Entregable: línea base segmentada.
- 3
Inspeccionar la ruta crítica
Revisar HTML inicial, fuentes, imágenes, JavaScript, almacenamiento en caché, respuesta del servidor y recursos de bloqueo. Dé un presupuesto explícito a los elementos que sirven al viaje.
Entregable: presupuesto de desempeño.
- 4
Reducir superficie expuesta
Inventario de scripts, dependencias, encabezados, cookies, sesiones, formularios e interfaces de administración de terceros. Elimine lo innecesario y endurezca el servidor.
Entregable: registro de dependencia y protección.
- 5
Experiencia inclusiva en pruebas
Ejecuta cada acción mediante teclado, lector de pantalla, pantalla pequeña, zoom y estado de error. Consulta etiquetas, mensajes de enfoque, contraste y recuperación.
Entregable: reporte de accesibilidad y fricción.
- 6
Liberación con barandillas
Automatizar controles estables, observar los resultados del negocio después del lanzamiento y preparar la reversión. Una solución se cierra cuando el viaje real mejora sin regresión.
Entregable: plan de validación continua.
Comprender, calcular y decidir
Core Web Vitals: interpretar el p75 y sus límites
LCP mide la carga del contenido principal; INP, la respuesta a las interacciones; CLS, la estabilidad visual. Use el percentil 75 y separe móvil y ordenador. El clasificador utiliza sus valores: no visita ni mide su sitio.
Anote URL o grupo, fechas, dispositivo y herramienta. Un resultado de laboratorio sirve para investigar una causa; no sustituye la distribución de visitas reales. La ausencia de INP no equivale a una respuesta instantánea.
Indicadores y pruebas
| Indicador | Interpretación | Prueba necesaria |
|---|---|---|
| LCP ≤ 2,5 s | Carga en el intervalo bueno | p75, elemento principal y demora de carga |
| INP ≤ 200 ms | Respuesta en el intervalo bueno | p75 e interacción lenta reproducida |
| CLS ≤ 0,1 | Estabilidad en el intervalo bueno | p75 y elemento que se desplaza |
Regla de cálculo
Bueno: LCP ≤ 2,5; INP ≤ 200; CLS ≤ 0,1. Malo: LCP > 4; INP > 500; CLS > 0,25. Entre ambos: necesita mejora.
Ejemplo trabajado ficticio
Situación ilustrativa
Una página de reserva parece rápida en un laboratorio pero su botón de confirmación responde lentamente en el móvil. El equipo segmenta las mediciones de campo por dispositivo y recorrido, luego prueba menos comportamiento de JavaScript y del teclado.
Decisión y pruebas esperadas
El cambio se acepta sólo si la tarea sigue siendo accesible, la interacción mejora y los controles de seguridad del viaje siguen funcionando.
Indicadores de gestión
| Indicador | Qué mide | Primera acción |
|---|---|---|
| Viaje exitoso | Usuarios completando la acción sin error de bloqueo | Arreglar primero los descansos compartidos por varios segmentos |
| Rendimiento en campo | Carga, interacción y estabilidad en dispositivos reales | Segmento antes de apuntar al cuello de botella dominante |
| Coste de terceros | Bytes, tiempo del hilo principal y solicitudes fuera del control directo | Eliminar, diferir o reemplazar a cada tercero no esencial |
| Tasa de errores | Fallos técnicos y de entrada por paso | Mejorar la prevención, mensajes y recuperación |
Errores comunes
- Optimizando solo la página de inicio
- Confundir una puntuación de laboratorio con una experiencia real
- Agregar una herramienta de seguridad sin eliminar riesgos innecesarios
- Dañar la accesibilidad o la medición para ahorrar milisegundos
Preguntas frecuentes
¿El rendimiento y la seguridad entran en conflicto?
No. Reducir las dependencias, JavaScript y las solicitudes innecesarias muchas veces mejora ambos. Las compensaciones deben medirse en función de los recorridos y riesgos reales.
¿A qué puntuación debemos apuntar?
Un umbral no reemplaza los datos del campo. Establezca presupuestos por recorrido, dispositivo y audiencia, luego realice un seguimiento junto con los resultados comerciales.
¿Por qué incluir la accesibilidad en la auditoría?
Porque una acción rápida que no se puede utilizar por teclado, entender o recuperar sigue siendo un fracaso comercial y de usuario.
Referencias: datos, usos y límites
Documentación consultada el .
Las notas detalladas de esta edición están disponibles en inglés.
| Fuente y finalidad | Dato o referencia verificada | Cómo utilizarla | Límite que debe conservarse |
|---|---|---|---|
| MDN · Cookie boundaries Understand session-cookie scope and SameSite boundaries. |
Secure, HttpOnly, SameSite and the __Host- prefix address different risks. A site can include multiple origins. | Test external navigation, subdomains, provider returns and authenticated operations separately. | Cookie configuration does not replace CSRF checks or server-side authorisation. |
Referencias IANA e interpretación DNSSEC
Las notas detalladas de esta edición están disponibles en inglés.
Distinguish resolution, caching and web responses
An outage can occur before any HTTP response. Examine DNS resolution, its validation and caches separately from the web server.
- Record the failing stage and the resolver involved.
- A received TTL and RRSIG expiration are different constraints.
- An error disappearing on one device does not prove recovery for all visitors.
Read the registries and try the cache model →
IETF · RFC 4033 · §3–5 · 2026-10-23
Extensiones: permisos y acceso
Las notas detalladas de esta edición están disponibles en inglés.
Include the browser in exposure scope
A hardened site can still be visited from a profile with highly authorised extensions. Keep the boundary between site security, browser capabilities and managed-endpoint choices visible.
- Inventory the test profile’s extensions with version and accountable owner.
- Explain each required host and check optional permissions actually granted.
- Test restriction and removal; static manifest reading cannot replace code and traffic observation.
Read the permission directory and manifest examples →
Microsoft Learn · Manage Microsoft Edge extensions using group policies · Enterprise policy documentation consulted 2026-10-23
CSP: directivas, alternativas y recorridos
Las notas detalladas de esta edición están disponibles en inglés.
CSP tells a browser which resources and certain behaviours a page permits. Reviewing it requires distinguishing the requested directive, its possible fallback, policy mode and delivery. A directive name in a header alone does not establish that a user journey is protected.
Twelve fallback chains extracted from CSP3 §6.8.3, three independent checks and eight fictional scenarios. Reference: W3C Working Draft of 16 September 2026, a work in progress rather than a final Recommendation. The consulted IANA registry contains sixteen names and was updated 3 February 2023.
W3C · Content Security Policy Level 3 · Mike West, Antonio Sartori · Working Draft · 2026-09-16 · work in progress · §2.2.1, §3, §6.8.3–6.8.4, §8.1
Twelve fallback orders and three checks without default-src
The selected list is not added to default-src. A present but empty directive also stops lookup. The final three rows are not fetch chains: base-uri, form-action and frame-ancestors require their own directive.
| Requested check | Lookup order · first present directive wins | Reference |
|---|---|---|
script-src-elem | script-src-elem → script-src → default-src | CSP3 §6.8.3 |
script-src-attr | script-src-attr → script-src → default-src | CSP3 §6.8.3 |
style-src-elem | style-src-elem → style-src → default-src | CSP3 §6.8.3 |
style-src-attr | style-src-attr → style-src → default-src | CSP3 §6.8.3 |
worker-src | worker-src → child-src → script-src → default-src | CSP3 §6.8.3 |
connect-src | connect-src → default-src | CSP3 §6.8.3 |
manifest-src | manifest-src → default-src | CSP3 §6.8.3 |
object-src | object-src → default-src | CSP3 §6.8.3 |
frame-src | frame-src → child-src → default-src | CSP3 §6.8.3 |
media-src | media-src → default-src | CSP3 §6.8.3 |
font-src | font-src → default-src | CSP3 §6.8.3 |
img-src | img-src → default-src | CSP3 §6.8.3 |
base-uri | base-uri | base-uri |
form-action | form-action | form-action |
frame-ancestors | frame-ancestors | frame-ancestors |
Taller de lectura CSP
Choose a case and a check. This workshop uses pre-separated example directives, keeps the first occurrence of each name and stops at the first directive present in the stated order. It does not parse arbitrary CSP or check source expressions, URLs, nonces, hashes, redirects or actual browser behaviour.
Each policy is read separately with its mode and delivery. Values are displayed as text; the workshop loads no resource named by an example.
Resultado por política
Delivery and mode: three different readings
| Mechanism | What to check | Limit |
|---|---|---|
| Content-Security-Policy | Response header and policies actually received. | Each enforced policy adds its constraint; a second cannot relax the first. |
| Content-Security-Policy-Report-Only | Violation observation and the configured reporting path. | Monitoring mode does not enforce this policy’s blocking. |
| meta http-equiv | Element position and content processed before it. | Report-Only, frame-ancestors, report-uri and sandbox are not supplied by this mechanism. |
Eight reading scenarios and acceptance exercises
C01 · Fallback to default-src
script-src-elem
1 · enforce · header
Content-Security-Policy: default-src 'none'Reading : script-src-elem and script-src are absent, so the chain reaches default-src. This list does not define base-uri, form-action or frame-ancestors.
Test to add : Select those three independent checks as well. Do not infer protection against embedding the page from default-src.
C02 · Fallback is not source-list merging
script-src-attr
1 · enforce · header
Content-Security-Policy: default-src 'none'; script-src 'self'Reading : script-src-attr reaches script-src before default-src. Their lists are not concatenated. The presence of self alone does not authorise an inline event handler.
Test to add : Test script elements, event attributes and other relevant mechanisms separately. The workshop selects a directive; it does not decide whether a script executes.
C03 · A worker reaches child-src before script-src
worker-src
1 · enforce · header
Content-Security-Policy: default-src 'none'; script-src 'self'; child-src https://frames.example.netReading : worker-src is absent. The first directive present in its fallback order is child-src. The word child does not mean only iframes are affected.
Test to add : Check workers and frames separately; record the selected control and observe the browser in its real context.
C04 · A specific directive stops fallback
worker-src
1 · enforce · header
Content-Security-Policy: default-src 'none'; child-src https://frames.example.net; worker-src 'self' blob:Reading : worker-src is present: neither child-src nor default-src supplies the list for this check. Its value is displayed without checking a URL, redirect or local scheme.
Test to add : Test creation and loading of expected workers together with their own policy and dependencies. Do not treat this illustrative list as universal configuration.
C05 · An empty directive is not absent
img-src
1 · enforce · header
Content-Security-Policy: img-src; img-src https://images.example.net; default-src 'self'Reading : The first img-src occurrence is retained with an empty list. The second occurrence is discarded in this policy; the workshop does not replace the first with default-src.
Test to add : Check duplicates in configuration and the received response. A present field without source expressions must not be treated as missing.
C06 · Two enforced policies remain two constraints
connect-src
1 · enforce · header
Content-Security-Policy: default-src 'self'; connect-src 'none'2 · enforce · header
Content-Security-Policy: connect-src https://api.example.netReading : The first policy retains connect-src none; the second names an origin. Adding the second does not lift the first policy’s restriction. Results are shown separately.
Test to add : Observe every received header after CDN and proxy handling. Do not unite both policies’ sources into a broader allowlist.
C07 · Monitoring is not enforcement
script-src-elem
1 · enforce · header
Content-Security-Policy: script-src 'self'2 · report-only · header
Content-Security-Policy-Report-Only: script-src 'none'Reading : script-src is selected in both policies. The second is Report-Only: it monitors violations without enforcing its blocking. The first retains its own effect.
Test to add : Plan report collection and check real journeys before a separately decided enforcement change. A monitored directive name alone does not establish blocking.
C08 · frame-ancestors in meta is ignored
frame-ancestors
1 · enforce · meta
<meta http-equiv="Content-Security-Policy" content="default-src 'none'; frame-ancestors 'none'">Reading : This directive is not supported in a meta-delivered policy. default-src remains a resource control rather than a fallback for frame-ancestors.
Test to add : Inspect the policy actually received in headers and authorised embeddings. A meta element cannot supply Report-Only mode either.
Sixteen IANA names: registration differs from support
CSP2 registry references are preserved verbatim. This copy does not list every CSP3 addition: absence of worker-src or script-src-elem does not invalidate those names in CSP3. Conversely, a historical name such as plugin-types does not establish support in a current browser.
IANA · Content Security Policy Directives · Registry updated 2023-02-03 · consulted 2026-10-23
| Registered name | Registry reference | Registration date |
|---|---|---|
base-uri | https://www.w3.org/TR/CSP2/ | 2015-11-24 |
child-src | https://www.w3.org/TR/CSP2/ | 2015-11-24 |
connect-src | https://www.w3.org/TR/CSP2/ | 2015-11-24 |
default-src | https://www.w3.org/TR/CSP2/ | 2015-11-24 |
font-src | https://www.w3.org/TR/CSP2/ | 2015-11-24 |
form-action | https://www.w3.org/TR/CSP2/ | 2015-11-24 |
frame-ancestors | https://www.w3.org/TR/CSP2/ | 2015-11-24 |
frame-src | https://www.w3.org/TR/CSP2/ | 2015-11-24 |
img-src | https://www.w3.org/TR/CSP2/ | 2015-11-24 |
media-src | https://www.w3.org/TR/CSP2/ | 2015-11-24 |
object-src | https://www.w3.org/TR/CSP2/ | 2015-11-24 |
plugin-types | https://www.w3.org/TR/CSP2/ | 2015-11-24 |
report-uri | https://www.w3.org/TR/CSP2/ | 2015-11-24 |
sandbox | https://www.w3.org/TR/CSP2/ | 2015-11-24 |
script-src | https://www.w3.org/TR/CSP2/ | 2015-11-24 |
style-src | https://www.w3.org/TR/CSP2/ | 2015-11-24 |
IANA · Protocol Registries · CC0 1.0 · Revised 2021-11-10
Test protection without breaking the journey
| Proposed CIE journey | Control to review | Useful evidence |
|---|---|---|
| Sign-in and recovery | Required scripts, styles, frames and connections. | Success, useful refusal, recovery and errors observed with received policies. |
| Payment or external integration | frame-src for embedded content; frame-ancestors for who embeds your page. | Test the two directions separately rather than conflate them. |
| Form and confirmation | form-action, validation scripts and API requests. | Submission and confirmation received; a click alone does not establish processing. |
| Worker and deferred features | worker-src and its fallback order. | Creation, dependent resources and visible errors in the authorised context. |
| Third-party addition | Inventory of actually required scripts, connections, images and frames. | Documented need and sampled journeys; no wildcard added to hide a breakage. |
| Progressive release | Observed mode, configuration version and stop criteria. | Reviewed reports, attributed defects, tests and an enforcement decision. |
Associate a policy with the page version and test critical journeys after CDN or proxy transformations. CSP is defence in depth: it does not replace output encoding, dependency control or access checks. This model explains directive selection rather than a security verdict.
Provenance, edition and licence
W3C CSP3 · Working Draft 2026-09-16 · reviewed 2026-10-23 · IANA registry 2023-02-03
IANA XML SHA-256: 42d2068b345f9b1df2bb124dd8b20e26d16dbd86960aafb62624aa285f2997c0
W3C HTML SHA-256: df90a9028632b39c70d9ed40dadfadbc2f3f690621ecf6212ef4f1376005738e
W3C · Software and Document license · 2023 · Effective 2023-01-01 · full notice below
This document and its lookup data include material derived from Content Security Policy Level 3, https://www.w3.org/TR/2026/WD-CSP3-20260916/. Copyright © 2026 World Wide Web Consortium. https://www.w3.org/copyright/software-license-2023/
Changes: selected fallback lists extracted as data; original CIE explanations, fictional scenarios and limited lookup implementation added.
This work is being provided by the copyright holders under the following license.
By obtaining and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions.
Permission to copy, modify, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the work or portions thereof, including modifications:
The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.
Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, the W3C software and document short notice should be included.
Notice of any changes or modifications, through a copyright statement on the new code or document such as "This software or document includes material copied from or derived from [title and URI of the W3C document]. Copyright © [$year-of-document] World Wide Web Consortium. https://www.w3.org/copyright/software-license-2023/"
THIS WORK IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENT WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENT.
The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the work without specific, written prior permission. Title to copyright in this work will at all times remain with copyright holders.
Core Web Vitals: umbrales y datos reales
Las notas detalladas de esta edición están disponibles en inglés.
Web performance: state the measurement scope
Before announcing a gain, retain device, URL or origin and collection period.
- Compare the same device, scope and documented periods.
- Do not turn missing data into zero.
- Verify functions and accessibility after the fix.
Read the thresholds and try the p75 reader →
Google · About PageSpeed Insights · Living documentation · consulted 2026-10-23
Referencias oficiales
Las referencias respaldan el método. Adapte los controles a su contexto; no constituyen certificación. Los títulos de referencia originales y los documentos fuente pueden estar en otro idioma.
Referencias consultadas el .
- Google Search Central — Core Web Vitals
- W3C — Web Content Accessibility Guidelines 2.2
- MDN · Cookie boundaries
- Google · About PageSpeed Insights
- W3C · Content Security Policy Level 3 · Mike West, Antonio Sartori
- IANA · Content Security Policy Directives
- Google Chrome · Declare permissions
- Microsoft Learn · Manage Microsoft Edge extensions using group policies
- IETF · RFC 4033 · DNSSEC introduction and requirements
- IETF · RFC 4035 · DNSSEC validation and caching
