Tools & Wizards About Us
ibroken.com.mx screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

ibroken.com.mx

Reparación de iPhone y Macbook | Ibroken | Centro Certificado CDMX

Page Load Speed

6.7 sec in total

First Response

242 ms

Resources Loaded

5.7 sec

Page Rendered

733 ms

ibroken.com.mx screenshot

About Website

Welcome to ibroken.com.mx homepage info - get ready to check Ibroken best content right away, or after learning these important things about ibroken.com.mx

Somos un centro certificado de servicio y reparación de dispositivos Apple y iPhone en la Ciudad de México. ¡Conocénos ahora!

Visit ibroken.com.mx

Key Findings

We analyzed Ibroken.com.mx page load time and found that the first response time was 242 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

ibroken.com.mx performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.7 s

0/100

25%

SI (Speed Index)

Value14.0 s

1/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.349

32/100

15%

TTI (Time to Interactive)

Value16.4 s

5/100

10%

Network Requests Diagram

www.ibroken.com.mx

242 ms

e7k71.css

106 ms

e7j79.css

101 ms

e7j79.css

114 ms

css

33 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 85% of them (72 requests) were addressed to the original Ibroken.com.mx, 7% (6 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Ibroken.com.mx.

Page Optimization Overview & Recommendations

Page size can be reduced by 336.8 kB (11%)

Content Size

3.0 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ibroken.com.mx main page is 3.0 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 147.2 kB

  • Original 191.5 kB
  • After minification 184.7 kB
  • After compression 44.3 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 147.2 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 45.5 kB

  • Original 2.0 MB
  • After minification 2.0 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Ibroken images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 104.3 kB

  • Original 662.0 kB
  • After minification 662.0 kB
  • After compression 557.7 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 104.3 kB or 16% of the original size.

CSS Optimization

-24%

Potential reduce by 39.7 kB

  • Original 165.8 kB
  • After minification 165.8 kB
  • After compression 126.1 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Ibroken.com.mx needs all CSS files to be minified and compressed as it can save up to 39.7 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 50 (67%)

Requests Now

75

After Optimization

25

  • Images
  • JavaScript
  • CSS

The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ibroken. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.ibroken.com.mx

www.ibroken.com.mx

242 ms

e7k71.css

e7k71.css

106 ms

e7j79.css

e7j79.css

101 ms

e7j79.css

e7j79.css

114 ms

css

css

33 ms

e7j79.css

e7j79.css

143 ms

e7j79.css

e7j79.css

174 ms

post-929.css

post-929.css

139 ms

e7j79.css

e7j79.css

173 ms

post-920.css

post-920.css

155 ms

e7j79.css

e7j79.css

233 ms

css

css

48 ms

e7j79.js

e7j79.js

300 ms

e7j79.js

e7j79.js

182 ms

js

js

68 ms

css

css

22 ms

wp-polyfill.min.js

wp-polyfill.min.js

209 ms

hooks.min.js

hooks.min.js

167 ms

i18n.min.js

i18n.min.js

169 ms

lodash.min.js

lodash.min.js

208 ms

url.min.js

url.min.js

209 ms

api-fetch.min.js

api-fetch.min.js

211 ms

index.js

index.js

235 ms

js.cookie.min.js

js.cookie.min.js

245 ms

woocommerce.min.js

woocommerce.min.js

239 ms

cart-fragments.min.js

cart-fragments.min.js

243 ms

wpcf7r-fe.js

wpcf7r-fe.js

251 ms

gtm4wp-contact-form-7-tracker.js

gtm4wp-contact-form-7-tracker.js

316 ms

jquery.easing.min.js

jquery.easing.min.js

316 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

317 ms

jquery.simpleplaceholder.js

jquery.simpleplaceholder.js

316 ms

imagesloaded.js

imagesloaded.js

317 ms

us.core.js

us.core.js

317 ms

us.widgets.js

us.widgets.js

328 ms

us.theme.js

us.theme.js

329 ms

comment-reply.min.js

comment-reply.min.js

329 ms

joinchat.min.js

joinchat.min.js

417 ms

wp-embed.min.js

wp-embed.min.js

417 ms

wpcf7-recaptcha-controls.js

wpcf7-recaptcha-controls.js

416 ms

api.js

api.js

30 ms

webpack.runtime.min.js

webpack.runtime.min.js

417 ms

frontend-modules.min.js

frontend-modules.min.js

491 ms

waypoints.min.js

waypoints.min.js

436 ms

core.min.js

core.min.js

426 ms

frontend.min.js

frontend.min.js

425 ms

gtm.js

gtm.js

54 ms

logo-web_color-300x81.png

logo-web_color-300x81.png

222 ms

transparent.png

transparent.png

221 ms

apple-devices.png

apple-devices.png

357 ms

iphone12.jpg

iphone12.jpg

272 ms

macbook.jpg

macbook.jpg

368 ms

iphone-11-pro-max.jpg

iphone-11-pro-max.jpg

340 ms

CE98AACF-CA02-4DE5-AC5B-042C857E1AC9.jpeg

CE98AACF-CA02-4DE5-AC5B-042C857E1AC9.jpeg

260 ms

ipad-1024x657.jpeg

ipad-1024x657.jpeg

301 ms

macbook-1024x1024.jpg

macbook-1024x1024.jpg

317 ms

repair-1024x683.jpg

repair-1024x683.jpg

336 ms

iphone.png

iphone.png

351 ms

color_front_green__eb8qbnemmre6_large.jpg

color_front_green__eb8qbnemmre6_large.jpg

354 ms

ipad.png

ipad.png

459 ms

watch.png

watch.png

388 ms

macbook.png

macbook.png

408 ms

happy-testimonial.png

happy-testimonial.png

397 ms

people-315076_960_720.jpg

people-315076_960_720.jpg

407 ms

10-real-people-who-are-winning-their-fight-with-debt.jpg

10-real-people-who-are-winning-their-fight-with-debt.jpg

408 ms

garantia_icon.png

garantia_icon.png

384 ms

horario_icon.png

horario_icon.png

395 ms

ubicacion_icon.png

ubicacion_icon.png

404 ms

pago_icon.png

pago_icon.png

406 ms

medios_pago.png

medios_pago.png

2407 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

100 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

173 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

175 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

175 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

176 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

176 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

428 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

436 ms

contenido3.jpg

contenido3.jpg

450 ms

wp-polyfill-fetch.min.js

wp-polyfill-fetch.min.js

292 ms

wp-polyfill-dom-rect.min.js

wp-polyfill-dom-rect.min.js

299 ms

wp-polyfill-url.min.js

wp-polyfill-url.min.js

313 ms

wp-polyfill-formdata.min.js

wp-polyfill-formdata.min.js

321 ms

wp-polyfill-element-closest.min.js

wp-polyfill-element-closest.min.js

324 ms

wp-polyfill-object-fit.min.js

wp-polyfill-object-fit.min.js

340 ms

recaptcha__es.js

recaptcha__es.js

22 ms

Accessibility Review

ibroken.com.mx accessibility score

65

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

ibroken.com.mx best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

ibroken.com.mx SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ibroken.com.mx can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Ibroken.com.mx main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

ibroken.com.mx

Open Graph data is detected on the main page of Ibroken. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: