Tools & Wizards About Us
imoi.es screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

imoi.es

IMOI, tu mejor dentista en Barcelona (Eixample) y en Ibiza.

Page Load Speed

5.4 sec in total

First Response

667 ms

Resources Loaded

2.6 sec

Page Rendered

2.1 sec

imoi.es screenshot

About Website

Welcome to imoi.es homepage info - get ready to check IMOI best content for Mexico right away, or after learning these important things about imoi.es

Equipo especializado experto 30 años contigo. Tu dentista de confianza en Barcelona (Eixample) y en Ibiza. ¡Te esperamos!

Visit imoi.es

Key Findings

We analyzed Imoi.es page load time and found that the first response time was 667 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

imoi.es performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

7/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value4.9 s

77/100

10%

Network Requests Diagram

www.imoi.es

667 ms

style.min.css

152 ms

style.min.css

230 ms

style.min.css

249 ms

theme.min.css

251 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 92% of them (56 requests) were addressed to the original Imoi.es, 3% (2 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Tracker.metricool.com. The less responsive or slowest element that took the longest time to load (781 ms) belongs to the original domain Imoi.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 403.1 kB (29%)

Content Size

1.4 MB

After Optimization

972.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Imoi.es main page is 1.4 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. 35% of websites need less resources to load. Images take 663.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 196.1 kB

  • Original 245.2 kB
  • After minification 237.3 kB
  • After compression 49.1 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 196.1 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 169 B

  • Original 663.2 kB
  • After minification 663.1 kB

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. IMOI images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 191.9 kB

  • Original 406.2 kB
  • After minification 406.2 kB
  • After compression 214.3 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 191.9 kB or 47% of the original size.

CSS Optimization

-25%

Potential reduce by 14.9 kB

  • Original 60.5 kB
  • After minification 60.3 kB
  • After compression 45.7 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. Imoi.es needs all CSS files to be minified and compressed as it can save up to 14.9 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (85%)

Requests Now

60

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.imoi.es

www.imoi.es

667 ms

style.min.css

style.min.css

152 ms

style.min.css

style.min.css

230 ms

style.min.css

style.min.css

249 ms

theme.min.css

theme.min.css

251 ms

frontend-lite.min.css

frontend-lite.min.css

335 ms

post-5.css

post-5.css

254 ms

frontend-lite.min.css

frontend-lite.min.css

255 ms

post-53.css

post-53.css

307 ms

post-12.css

post-12.css

327 ms

post-38.css

post-38.css

329 ms

style.css

style.css

338 ms

language-cookie.js

language-cookie.js

349 ms

js

js

97 ms

js

js

189 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

382 ms

widget-icon-list.min.css

widget-icon-list.min.css

403 ms

widget-carousel.min.css

widget-carousel.min.css

407 ms

cookieconsent.js

cookieconsent.js

343 ms

post-1004.css

post-1004.css

342 ms

post-938.css

post-938.css

346 ms

post-1236.css

post-1236.css

387 ms

post-1007.css

post-1007.css

412 ms

frontend.min.css

frontend.min.css

419 ms

aare.css

aare.css

422 ms

aare.css

aare.css

423 ms

default.css

default.css

428 ms

webfont.js

webfont.js

510 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

510 ms

imagesloaded.min.js

imagesloaded.min.js

510 ms

js

js

93 ms

masonry.min.js

masonry.min.js

510 ms

jquery.masonry.min.js

jquery.masonry.min.js

510 ms

maps.min.js

maps.min.js

593 ms

frontend.min.js

frontend.min.js

541 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

567 ms

webpack.runtime.min.js

webpack.runtime.min.js

576 ms

frontend-modules.min.js

frontend-modules.min.js

584 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

583 ms

wp-polyfill.min.js

wp-polyfill.min.js

617 ms

hooks.min.js

hooks.min.js

573 ms

i18n.min.js

i18n.min.js

509 ms

frontend.min.js

frontend.min.js

499 ms

waypoints.min.js

waypoints.min.js

498 ms

core.min.js

core.min.js

501 ms

frontend.min.js

frontend.min.js

519 ms

elements-handlers.min.js

elements-handlers.min.js

496 ms

lazyload.min.js

lazyload.min.js

490 ms

be.js

be.js

245 ms

IMG-5.jpg

IMG-5.jpg

781 ms

IMG-16.jpg

IMG-16.jpg

459 ms

IMG-24.jpg

IMG-24.jpg

390 ms

IMG-229.jpg

IMG-229.jpg

474 ms

c3po.jpg

c3po.jpg

126 ms

es.png

es.png

81 ms

en.png

en.png

79 ms

ca.png

ca.png

157 ms

avatar.svg

avatar.svg

159 ms

phone.svg

phone.svg

181 ms

whatsapp.svg

whatsapp.svg

235 ms

envelope.svg

envelope.svg

239 ms

Accessibility Review

imoi.es accessibility score

96

Accessibility Issues

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.

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

Links do not have a discernible name

Best Practices

imoi.es best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

imoi.es SEO score

99

Search Engine Optimization Advices

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

imoi.es

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