Tools & Wizards About Us
lector.mx screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

lector.mx

Lector México – Libros de editoriales independientes mexicanas

Page Load Speed

2 sec in total

First Response

323 ms

Resources Loaded

1.3 sec

Page Rendered

382 ms

lector.mx screenshot

About Website

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

Plan lector - Lectores Esfinge es una propuesta para crear comunidades de lectores en las escuelas y fomentar el hábito de la lectura. Está dirigido a estudiantes, maestros y padres de familia.

Visit lector.mx

Key Findings

We analyzed Lector.mx page load time and found that the first response time was 323 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

lector.mx performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value6.4 s

41/100

10%

TBT (Total Blocking Time)

Value190 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.23

54/100

15%

TTI (Time to Interactive)

Value7.1 s

52/100

10%

Network Requests Diagram

lector.mx

323 ms

estilos.css

64 ms

actionSist.js

45 ms

default.css

109 ms

nivo-slider.css

105 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 96% of them (45 requests) were addressed to the original Lector.mx, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (562 ms) belongs to the original domain Lector.mx.

Page Optimization Overview & Recommendations

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

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lector.mx main page is 1.3 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. 25% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 24.0 kB

  • Original 29.9 kB
  • After minification 24.0 kB
  • After compression 5.9 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 5.9 kB, which is 20% 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 24.0 kB or 80% of the original size.

Image Optimization

-12%

Potential reduce by 153.3 kB

  • Original 1.3 MB
  • After minification 1.1 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. Obviously, Lector needs image optimization as it can save up to 153.3 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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

-39%

Potential reduce by 573 B

  • Original 1.5 kB
  • After minification 1.4 kB
  • After compression 894 B

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. Lector.mx needs all CSS files to be minified and compressed as it can save up to 573 B or 39% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (33%)

Requests Now

45

After Optimization

30

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lector.mx

lector.mx

323 ms

estilos.css

estilos.css

64 ms

actionSist.js

actionSist.js

45 ms

default.css

default.css

109 ms

nivo-slider.css

nivo-slider.css

105 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

214 ms

functions.js

functions.js

81 ms

jquery.nivo.slider.pack.js

jquery.nivo.slider.pack.js

106 ms

ga.js

ga.js

60 ms

fondo_esfinge.jpg

fondo_esfinge.jpg

218 ms

plaeca_top.png

plaeca_top.png

53 ms

bg_login.jpg

bg_login.jpg

69 ms

bg_menu.jpg

bg_menu.jpg

94 ms

lectoresEsfinge.png

lectoresEsfinge.png

55 ms

line_Sidebar.jpg

line_Sidebar.jpg

51 ms

bar_banner.png

bar_banner.png

88 ms

banerlectores1.jpg

banerlectores1.jpg

210 ms

banerlectores2.jpg

banerlectores2.jpg

178 ms

banerpoemas.jpg

banerpoemas.jpg

202 ms

0025%20Banner%20Cuentos%20mexicanos.jpg

0025%20Banner%20Cuentos%20mexicanos.jpg

202 ms

Banner_persona%20normal.png

Banner_persona%20normal.png

255 ms

bar_rosa_lf.jpg

bar_rosa_lf.jpg

201 ms

personanormal.jpg

personanormal.jpg

336 ms

la-luz-que-regresa-4-218-9.jpg

la-luz-que-regresa-4-218-9.jpg

264 ms

abc-un-invento-4-191-9.jpg

abc-un-invento-4-191-9.jpg

270 ms

cuentos-piratas-corsarios-4-117-X.jpg

cuentos-piratas-corsarios-4-117-X.jpg

311 ms

16-cuentos-latinoamericanos-4-064-5.jpg

16-cuentos-latinoamericanos-4-064-5.jpg

272 ms

bg_search.png

bg_search.png

313 ms

btn_search.jpg

btn_search.jpg

370 ms

btn_search2.jpg

btn_search2.jpg

312 ms

sep_sidebar.jpg

sep_sidebar.jpg

295 ms

bg_botones_side.jpg

bg_botones_side.jpg

343 ms

icono_recursos.png

icono_recursos.png

342 ms

icono_catalogo.png

icono_catalogo.png

341 ms

icono_videos.png

icono_videos.png

353 ms

icono_testimonios.png

icono_testimonios.png

355 ms

icono_noticias_eventos.png

icono_noticias_eventos.png

363 ms

icono_ligas.png

icono_ligas.png

364 ms

bg_footer.jpg

bg_footer.jpg

388 ms

esfinge_footer.jpg

esfinge_footer.jpg

374 ms

youtube.jpg

youtube.jpg

402 ms

facebook.jpg

facebook.jpg

387 ms

sombra.png

sombra.png

400 ms

UbuntuCondensed-Regular.ttf

UbuntuCondensed-Regular.ttf

562 ms

__utm.gif

__utm.gif

12 ms

arrows.png

arrows.png

137 ms

bullets.png

bullets.png

24 ms

Accessibility Review

lector.mx accessibility score

72

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 have valid values

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Best Practices

lector.mx best practices score

83

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

lector.mx SEO score

75

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lector.mx can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lector.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

lector.mx

Open Graph description is not detected on the main page of Lector. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: