Logo

Resumen automático de Amazon Counter - F Ahorro Juarez 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 Amazon Counter - F Ahorro Juarez ubicada en Estado de México, México y dedicada al sector Servicio postal, cuenta con el sitio web www.amazon.com.mx/ulp/add-ap-to-address-book?countryCode=MX&accessPointId=1002fbdf-52d6-4bc8-a201-8dff1ba5a7f5&ref_=hubm_mx_gm_coutr_1002fbdf-52d6-4bc8-a201-8dff1ba5a7f5, así como un perfil en Google Maps.

A continuación se muestran los canales de presencia digital disponibles:

Executive Summary

Performance

Score: 74/100

Acceptable, but improvements are recommended.

Among the detected issues:

  • Stylesheets are unminified, impacting load time.
  • 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.
  • Some CSS rules are unused.
  • Unused JavaScript detected.
  • Scripts are unminified, increasing payload size.
  • Text compression (gzip, brotli) not enabled.

Accessibility

Score: 95/100

Excellent result in this category.

Best Practices

Score: 96/100

Excellent result in this category.

Among the detected issues:

  • Missing adequate CSP headers against XSS.
  • Potential vulnerabilities in third‑party JS libraries.

SEO

Score: 92/100

Excellent result in this category.


Technical Analysis

Opportunities

Minify CSS

Efficiently encode images

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 18 KiB

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: 290 ms

Preload Largest Contentful Paint image

Preconnect to required origins

Initial server response time was short

Avoid multiple page redirects

Eliminate render-blocking resources

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.
  • Potential Savings: Potential savings of 83 KiB

Remove duplicate modules in JavaScript bundles

  • Description: Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

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: Potential savings of 126 KiB

Minify JavaScript

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: Potential savings of 249 KiB

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: Potential savings of 315 KiB

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

Enable text compression

Diagnostics

Resources Summary

  • Description: Aggregates all network requests and groups them by type

Avoid non-composited animations

Tasks

  • Description: Lists the toplevel main thread tasks that executed during page load.

Screenshot Thumbnails

  • Description: This is what the load of your site looked like.

Ensure CSP is effective against XSS attacks

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: 40 ms
  • Numeric Value: 40.5

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: 60 ms
  • Numeric Value: 60.644025

Final Screenshot

  • Description: The last screenshot captured of the pageload.

Detected JavaScript libraries

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.

Metrics

  • Description: Collects all available metrics.
  • Numeric Value: 9911

Ensure proper origin isolation with COOP

Avoid long main-thread tasks

Script Treemap Data

  • Description: Used for treemap app

Diagnostics

  • Description: Collection of useful page vitals.

Network Requests

  • Description: Lists the network requests that were made during page load.

Minimize third-party usage

  • Description: Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.
  • Display Value: Third-party code blocked the main thread for 100 ms

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: 9 chains found

Report generated on 26/4/2025, 11:36:29

© 2025 Synara LLC. Informe generado automáticamente con PageSpeed Insights API.