Tools & Wizards About Us
celularess.com screenshot

Report Summary

  • 1

    Performance

    Renders faster than
    19% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

celularess.com

CelularesS- Especificaciones de todos los celulares de todas las marcas

Page Load Speed

6.7 sec in total

First Response

1.9 sec

Resources Loaded

4.6 sec

Page Rendered

170 ms

celularess.com screenshot

About Website

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

En celularess.com puedes encontrar todos los celulares de todas las marcas y sus especificaciones, reviews y comparaciones. Encuenta el celular que deseas.

Visit celularess.com

Key Findings

We analyzed Celularess.com page load time and found that the first response time was 1.9 sec and then it took 4.8 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

celularess.com performance score

1

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.1 s

0/100

25%

SI (Speed Index)

Value20.9 s

0/100

10%

TBT (Total Blocking Time)

Value5,060 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.666

8/100

15%

TTI (Time to Interactive)

Value23.0 s

1/100

10%

Network Requests Diagram

celularess.com

1860 ms

wp-emoji-release.min.js

44 ms

style.min.css

83 ms

rs6.css

112 ms

css

36 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 84% of them (57 requests) were addressed to the original Celularess.com, 3% (2 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Celularess.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 146.9 kB (13%)

Content Size

1.1 MB

After Optimization

981.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Celularess.com main page is 1.1 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. Javascripts take 474.6 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 97.3 kB

  • Original 116.5 kB
  • After minification 101.9 kB
  • After compression 19.2 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. This page needs HTML code to be minified as it can gain 14.6 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 97.3 kB or 84% of the original size.

Image Optimization

-8%

Potential reduce by 28.3 kB

  • Original 362.5 kB
  • After minification 334.2 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. CelularesS images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 7.9 kB

  • Original 474.6 kB
  • After minification 474.6 kB
  • After compression 466.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-8%

Potential reduce by 13.4 kB

  • Original 174.9 kB
  • After minification 174.9 kB
  • After compression 161.5 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. Celularess.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 38 (62%)

Requests Now

61

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CelularesS. 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 14 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

celularess.com

celularess.com

1860 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

44 ms

style.min.css

style.min.css

83 ms

rs6.css

rs6.css

112 ms

css

css

36 ms

js_composer.min.css

js_composer.min.css

182 ms

style.css

style.css

420 ms

eggrehub.css

eggrehub.css

296 ms

style.css

style.css

330 ms

responsive.css

responsive.css

157 ms

css.css

css.css

154 ms

font-awesome.min.css

font-awesome.min.css

226 ms

aps-styles.css

aps-styles.css

230 ms

imageviewer.css

imageviewer.css

327 ms

nivo-lightbox.css

nivo-lightbox.css

277 ms

owl-carousel.css

owl-carousel.css

286 ms

jquery.js

jquery.js

355 ms

jquery-migrate.min.js

jquery-migrate.min.js

342 ms

price_alert.js

price_alert.js

362 ms

revolution.tools.min.js

revolution.tools.min.js

370 ms

rs6.min.js

rs6.min.js

484 ms

imageviewer.min.js

imageviewer.min.js

395 ms

js

js

64 ms

adsbygoogle.js

adsbygoogle.js

199 ms

inview.js

inview.js

395 ms

pgwmodal.js

pgwmodal.js

410 ms

unveil.js

unveil.js

413 ms

cuttabs.js

cuttabs.js

479 ms

hoverintent.js

hoverintent.js

478 ms

niceselect.js

niceselect.js

479 ms

countdown.js

countdown.js

478 ms

custom.js

custom.js

480 ms

jquery.sticky.js

jquery.sticky.js

542 ms

comment-reply.min.js

comment-reply.min.js

542 ms

nivo-lightbox.min.js

nivo-lightbox.min.js

542 ms

owl.carousel.min.js

owl.carousel.min.js

543 ms

aps-main-script-min.js

aps-main-script-min.js

599 ms

wp-embed.min.js

wp-embed.min.js

544 ms

minilogo.png

minilogo.png

304 ms

Logo-azul.png

Logo-azul.png

115 ms

ZTE-Blade-20-Pro-5G-300x300.jpg

ZTE-Blade-20-Pro-5G-300x300.jpg

102 ms

ZTE-Blade-V2020-5G.png

ZTE-Blade-V2020-5G.png

161 ms

Honor-10X-Lite-300x300.jpg

Honor-10X-Lite-300x300.jpg

115 ms

ZTE-Blade-20-5G-300x300.jpg

ZTE-Blade-20-5G-300x300.jpg

135 ms

Honor-30i-300x300.jpg

Honor-30i-300x300.jpg

136 ms

ZTE-Blade-A7s-2020-300x300.jpg

ZTE-Blade-A7s-2020-300x300.jpg

157 ms

Honor-X10-Max-5G-300x300.png

Honor-X10-Max-5G-300x300.png

212 ms

ZTE-Axon-20-5G-Extreme-300x300.png

ZTE-Axon-20-5G-Extreme-300x300.png

233 ms

Honor-30-Youth-300x300.jpeg

Honor-30-Youth-300x300.jpeg

212 ms

ZTE-Axon-20-5G-300x300.jpg

ZTE-Axon-20-5G-300x300.jpg

212 ms

Honor-8S-2020-300x300.jpg

Honor-8S-2020-300x300.jpg

215 ms

ZTE-Axon-20-4G-300x300.jpg

ZTE-Axon-20-4G-300x300.jpg

214 ms

Vs-general-71x50.jpg

Vs-general-71x50.jpg

214 ms

Huawei-Mate-30-120x120.jpg

Huawei-Mate-30-120x120.jpg

301 ms

OnePlus-3T-120x120.jpg

OnePlus-3T-120x120.jpg

242 ms

HTC-One-X10-120x120.png

HTC-One-X10-120x120.png

300 ms

Logo-blanco-u.png

Logo-blanco-u.png

299 ms

js

js

76 ms

analytics.js

analytics.js

72 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

73 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

73 ms

fa-light-300.woff

fa-light-300.woff

423 ms

fa-regular-400.woff

fa-regular-400.woff

357 ms

fa-solid-900.woff

fa-solid-900.woff

422 ms

zrt_lookup.html

zrt_lookup.html

59 ms

show_ads_impl.js

show_ads_impl.js

326 ms

aps-icons.woff

aps-icons.woff

227 ms

collect

collect

18 ms

Accessibility Review

celularess.com accessibility score

79

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

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

celularess.com best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

celularess.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    EN

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Celularess.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Spanish language. Our system also found out that Celularess.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

celularess.com

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