Resumen automático de Avena - Software para Nutriólogos generado por Synara
Informe de rendimiento en Mobile. Ver rendimiento en desktop
Synara localiza negocios en Google Maps, valida teléfonos con WhatsApp y mide el rendimiento con PageSpeed Insights, enriqueciendo los datos con redes sociales para ofrecerte este informe SEO.
La empresa Avena - Software para Nutriólogos ubicada en ZAPOPAN, MEXICO y dedicada al sector Empresa de software, cuenta con el sitio web avena.io/, así como un perfil en Google Maps, donde ostenta 11 reseñas. Su teléfono de contacto es +523321919737.
A continuación se muestran los canales de presencia digital disponibles:
Executive Summary
Performance
Score: 52/100
Limited performance; optimisation needed.
Among the detected issues:
- Text compression (gzip, brotli) not enabled.
- Images are not compressed/optimized, affecting load times.
- Server response time is slow (TTFB).
- There are resources blocking the initial render; inline or defer them.
- Stylesheets are unminified, impacting load time.
- Some CSS rules are unused.
- Scripts are unminified, increasing payload size.
- Unused JavaScript detected.
Accessibility
Score: 86/100
Good overall performance; minor tweaks possible.
Among the detected issues:
- Video lacks captions, affecting accessibility.
Best Practices
Score: 79/100
Acceptable, but improvements are recommended.
Among the detected issues:
- Potential vulnerabilities in third‑party JS libraries.
- Missing adequate CSP headers against XSS.
SEO
Score: 100/100
Excellent result in this category.
Technical Analysis
Opportunities
Enable text compression
- Description: Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Efficiently encode images
- Description: Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Remove duplicate modules in JavaScript bundles
- Description: Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Initial server response time was short
- Description: Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
- Potential Savings: Root document took 60 ms
Serve images in next-gen formats
- Description: Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
- Potential Savings: 150 ms
Avoid multiple page redirects
- Description: Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Defer offscreen images
- Description: Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
- Potential Savings: 180 ms
Eliminate render-blocking resources
- Description: Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
- Potential Savings: 300 ms
Preconnect to required origins
- Description: Consider adding
preconnect
ordns-prefetch
resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.
Minify CSS
- Description: Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Avoid serving legacy JavaScript to modern browsers
- Description: Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to serve modern JavaScript
- Potential Savings: Potential savings of 20 KiB
Reduce unused CSS
- Description: Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Properly size images
- Description: Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
- Potential Savings: 150 ms
Use video formats for animated content
- Description: Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formats
Minify JavaScript
- Description: Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
- Potential Savings: Potential savings of 3 KiB
Reduce unused JavaScript
- Description: Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
- Potential Savings: 1370 ms
Diagnostics
Tasks
- Description: Lists the toplevel main thread tasks that executed during page load.
Detected JavaScript libraries
- Description: All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Final Screenshot
- Description: The last screenshot captured of the pageload.
<video>
elements contain a <track>
element with [kind="captions"]
- Description: When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
Document has a main landmark.
- Description: One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Diagnostics
- Description: Collection of useful page vitals.
Identical links have the same purpose.
- Description: Links with the same destination should have the same description, to help users understand the link's purpose and decide whether to follow it. Learn more about identical links.
Script Treemap Data
- Description: Used for treemap app
Server Backend Latencies
- Description: Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more about server response time.
- Display Value: 20 ms
- Numeric Value: 16
Metrics
- Description: Collects all available metrics.
- Numeric Value: 14804
Ensure proper origin isolation with COOP
- Description: The Cross-Origin-Opener-Policy (COOP) can be used to isolate the top-level window from other documents such as pop-ups. Learn more about deploying the COOP header.
Network Requests
- Description: Lists the network requests that were made during page load.
Ensure CSP is effective against XSS attacks
- Description: A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Avoid chaining critical requests
- Description: The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.
- Display Value: 10 chains found
Screenshot Thumbnails
- Description: This is what the load of your site looked like.
Network Round Trip Times
- Description: Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more about the Round Trip Time.
- Display Value: 20 ms
- Numeric Value: 22.14594
Mitigate clickjacking with XFO or CSP
- Description: The
X-Frame-Options
(XFO) header or theframe-ancestors
directive in theContent-Security-Policy
(CSP) header control where a page can be embedded. These can mitigate clickjacking attacks by blocking some or all sites from embedding the page. Learn more about mitigating clickjacking.
Use a strong HSTS policy
- Description: Deployment of the HSTS header significantly reduces the risk of downgrading HTTP connections and eavesdropping attacks. A rollout in stages, starting with a low max-age is recommended. Learn more about using a strong HSTS policy.
Avoid long main-thread tasks
- Description: Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks
- Display Value: 12 long tasks found
Resources Summary
- Description: Aggregates all network requests and groups them by type
Report generated on 26/4/2025, 01:06:52
© 2025 Synara LLC. Informe generado automáticamente con PageSpeed Insights API.