Logo

Resumen automático de BID Capital 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 BID Capital ubicada en Ciudad de México, México y dedicada al sector Banco de inversión, cuenta con el sitio web www.bidg.mx/, así como un perfil en Google Maps, donde ostenta 1 reseñas. Su teléfono de contacto es +525552027557.

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

Executive Summary

Performance

Score: 64/100

Limited performance; optimisation needed.

Among the detected issues:

  • Scripts are unminified, increasing payload size.
  • There are resources blocking the initial render; inline or defer them.
  • Images are not compressed/optimized, affecting load times.
  • Some CSS rules are unused.
  • Stylesheets are unminified, impacting load time.
  • Server response time is slow (TTFB).
  • Text compression (gzip, brotli) not enabled.
  • Unused JavaScript detected.

Accessibility

Score: 90/100

Excellent result in this category.

Best Practices

Score: 100/100

Excellent result in this category.

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

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

Minify JavaScript

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

Eliminate render-blocking resources

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.

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.

Minify CSS

Preload Largest Contentful Paint image

Properly size images

  • Description: Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.

Reduce initial server response time

Enable text compression

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

Avoid multiple page redirects

Preconnect to required origins

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: 140 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

Diagnostics

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

Mitigate clickjacking with XFO or CSP

  • Description: The X-Frame-Options (XFO) header or the frame-ancestors directive in the Content-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.

Detected JavaScript libraries

Ensure proper origin isolation with COOP

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 50 ms

Final Screenshot

  • Description: The last screenshot captured of the pageload.

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.

Metrics

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

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: 50 ms
  • Numeric Value: 51

Avoid long main-thread tasks

Diagnostics

  • Description: Collection of useful page vitals.

Tasks

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

Resources Summary

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

Ensure CSP is effective against XSS attacks

Avoid non-composited animations

Script Treemap Data

  • Description: Used for treemap app

Network Requests

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

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

Screenshot Thumbnails

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

Report generated on 26/4/2025, 12:49:06

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