Tools & Wizards About Us
cliba.com screenshot

Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

cliba.com

Inicio - Cliba

Page Load Speed

12.6 sec in total

First Response

49 ms

Resources Loaded

12.2 sec

Page Rendered

333 ms

cliba.com screenshot

About Website

Click here to check amazing Cliba content. Otherwise, check out these important facts you probably never knew about cliba.com

Esta empresa está dedicada a la importación, comercialización/distribución de dispositivos y medicamentos para la obesidad.

Visit cliba.com

Key Findings

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

Performance Metrics

cliba.com performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value150 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value5.4 s

72/100

10%

Network Requests Diagram

cliba.com

49 ms

cliba.com

11694 ms

wp-emoji-release.min.js

25 ms

style.min.css

47 ms

classic-themes.min.css

56 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 85% of them (57 requests) were addressed to the original Cliba.com, 13% (9 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (11.7 sec) belongs to the original domain Cliba.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 108.1 kB (65%)

Content Size

167.2 kB

After Optimization

59.1 kB

  • HTML
  • Images

In fact, the total size of Cliba.com main page is 167.2 kB. 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. HTML takes 128.1 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 105.5 kB

  • Original 128.1 kB
  • After minification 122.5 kB
  • After compression 22.6 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 105.5 kB or 82% of the original size.

Image Optimization

-7%

Potential reduce by 2.6 kB

  • Original 39.2 kB
  • After minification 36.5 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. Cliba images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 40 (75%)

Requests Now

53

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cliba.com

cliba.com

49 ms

cliba.com

cliba.com

11694 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

25 ms

style.min.css

style.min.css

47 ms

classic-themes.min.css

classic-themes.min.css

56 ms

ht-slider-widgets.css

ht-slider-widgets.css

55 ms

global.min.css

global.min.css

63 ms

header.min.css

header.min.css

63 ms

content.min.css

content.min.css

64 ms

footer.min.css

footer.min.css

66 ms

elementor-icons.min.css

elementor-icons.min.css

72 ms

frontend-lite.min.css

frontend-lite.min.css

73 ms

post-5.css

post-5.css

82 ms

frontend-lite.min.css

frontend-lite.min.css

85 ms

global.css

global.css

86 ms

post-563.css

post-563.css

86 ms

post-502.css

post-502.css

89 ms

post-517.css

post-517.css

91 ms

gdpr-main.css

gdpr-main.css

105 ms

css

css

33 ms

fontawesome.min.css

fontawesome.min.css

108 ms

brands.min.css

brands.min.css

111 ms

solid.min.css

solid.min.css

111 ms

regular.min.css

regular.min.css

106 ms

jquery.min.js

jquery.min.js

127 ms

jquery-migrate.min.js

jquery-migrate.min.js

125 ms

widget-icon-list.min.css

widget-icon-list.min.css

124 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

155 ms

animations.min.css

animations.min.css

285 ms

navigation.min.js

navigation.min.js

294 ms

main.js

main.js

295 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

293 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

294 ms

webpack.runtime.min.js

webpack.runtime.min.js

295 ms

frontend-modules.min.js

frontend-modules.min.js

295 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

294 ms

wp-polyfill.min.js

wp-polyfill.min.js

308 ms

hooks.min.js

hooks.min.js

307 ms

i18n.min.js

i18n.min.js

313 ms

frontend.min.js

frontend.min.js

303 ms

waypoints.min.js

waypoints.min.js

276 ms

core.min.js

core.min.js

273 ms

frontend.min.js

frontend.min.js

276 ms

elements-handlers.min.js

elements-handlers.min.js

268 ms

Recurso-1-1.svg

Recurso-1-1.svg

194 ms

Recurso-11f.png

Recurso-11f.png

195 ms

Recurso-13f.webp

Recurso-13f.webp

199 ms

Recurso-14f.webp

Recurso-14f.webp

196 ms

Recurso-15f.webp

Recurso-15f.webp

199 ms

Recurso-16f.webp

Recurso-16f.webp

196 ms

Recurso-3.svg

Recurso-3.svg

197 ms

Garantia-Allurion@3x-100-284x300.jpg

Garantia-Allurion@3x-100-284x300.jpg

199 ms

Recurso-12f-e1669381045225.webp

Recurso-12f-e1669381045225.webp

119 ms

Recurso-17f-e1669387167559.webp

Recurso-17f-e1669387167559.webp

75 ms

Recurso-175r.webp

Recurso-175r.webp

75 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

64 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

71 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

107 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

114 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

117 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

115 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

117 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

115 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

114 ms

fa-solid-900.woff

fa-solid-900.woff

146 ms

fa-regular-400.woff

fa-regular-400.woff

62 ms

fa-brands-400.woff

fa-brands-400.woff

106 ms

Accessibility Review

cliba.com accessibility score

98

Accessibility Issues

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

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

cliba.com SEO score

100

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

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

cliba.com

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