Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

aulex.ohui.net

AULEX - Diccionarios para autodidactas AULEX

Page Load Speed

800 ms in total

First Response

222 ms

Resources Loaded

459 ms

Page Rendered

119 ms

aulex.ohui.net screenshot

About Website

Visit aulex.ohui.net now to see the best up-to-date AULEX Ohui content for Mexico and also check out these interesting facts you probably never knew about aulex.ohui.net

Diccionarios para autodidactas Aulex: japonés, chino, árabe, náhuatl, maya, otomí, zapoteco, tarasco, mixteco, quechua, esperanto, catalán, gallego, asturiano e hindi

Visit aulex.ohui.net

Key Findings

We analyzed Aulex.ohui.net page load time and found that the first response time was 222 ms and then it took 578 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

aulex.ohui.net performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

89/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

83/100

25%

SI (Speed Index)

Value3.2 s

91/100

10%

TBT (Total Blocking Time)

Value1,090 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.235

53/100

15%

TTI (Time to Interactive)

Value8.2 s

41/100

10%

Network Requests Diagram

aulex.ohui.net

222 ms

aulex.org

211 ms

urchin.js

8 ms

__utm.gif

4 ms

Our browser made a total of 4 requests to load all elements on the main page. We found that 25% of them (1 request) were addressed to the original Aulex.ohui.net, 50% (2 requests) were made to Google-analytics.com and 25% (1 request) were made to Aulex.org. The less responsive or slowest element that took the longest time to load (222 ms) belongs to the original domain Aulex.ohui.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.7 kB (33%)

Content Size

11.1 kB

After Optimization

7.4 kB

In fact, the total size of Aulex.ohui.net main page is 11.1 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Javascripts take 6.8 kB which makes up the majority of the site volume.

HTML Optimization

-64%

Potential reduce by 2.7 kB

  • Original 4.3 kB
  • After minification 3.7 kB
  • After compression 1.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. This page needs HTML code to be minified as it can gain 619 B, which is 14% 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 2.7 kB or 64% of the original size.

JavaScript Optimization

-14%

Potential reduce by 971 B

  • Original 6.8 kB
  • After minification 6.8 kB
  • After compression 5.9 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 971 B or 14% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

2

After Optimization

2

The browser has sent 2 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AULEX Ohui. According to our analytics all requests are already optimized.

Accessibility Review

aulex.ohui.net accessibility score

80

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

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

aulex.ohui.net 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

SEO Factors

aulex.ohui.net 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 Aulex.ohui.net 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 Aulex.ohui.net 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

Open Graph description is not detected on the main page of AULEX Ohui. 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: