Logo

Resumen automático de IQVIA 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 IQVIA ubicada en Ciudad Autónoma de Buenos Aires, Argentina y dedicada al sector Oficinas de empresa, cuenta con el sitio web www.iqvia.com/locations/argentina, así como un perfil en Google Maps, donde ostenta 23 reseñas. Su teléfono de contacto es +541141236700.

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

Executive Summary

Performance

Score: 27/100

Very low score; major improvements required.

Among the detected issues:

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

Accessibility

Score: 73/100

Acceptable, but improvements are recommended.

Among the detected issues:

  • Video lacks captions, affecting accessibility.

Best Practices

Score: 93/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: 77/100

Acceptable, but improvements are recommended.


Technical Analysis

Opportunities

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

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

Preload Largest Contentful Paint image

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

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

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

Efficiently encode images

Minify JavaScript

  • Description: Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
  • Potential Savings: Potential savings of 101 KiB

Preconnect to required origins

Minify CSS

  • Description: Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
  • Potential Savings: 300 ms

Avoid multiple page redirects

Remove duplicate modules in JavaScript bundles

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

Eliminate render-blocking resources

Initial server response time was short

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 8 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.
  • Potential Savings: 2080 ms

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.
  • Potential Savings: 150 ms

Diagnostics

Avoid long main-thread tasks

Avoid large layout shifts

  • Description: These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
  • Display Value: 11 layout shifts found

Avoid non-composited animations

Screenshot Thumbnails

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

User Timing marks and measures

  • Description: Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
  • Display Value: 48 user timings

Tasks

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

<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.

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.

Diagnostics

  • Description: Collection of useful page vitals.

Ensure CSP is effective against XSS attacks

Network Requests

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

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: 130 ms
  • Numeric Value: 128

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

Final Screenshot

  • Description: The last screenshot captured of the pageload.

Metrics

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

Ensure proper origin isolation with COOP

Script Treemap Data

  • Description: Used for treemap app

Detected JavaScript libraries

Resources Summary

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

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: 10 ms
  • Numeric Value: 10.818719999999999

Report generated on 27/4/2025, 12:03:40

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