Tools & Wizards About Us
otakod.es screenshot

Report Summary

  • 96

    Performance

    Renders faster than
    94% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

otakod.es

Ariel Dorol - freelance front-end web developer & Javascript teacher

Page Load Speed

1.1 sec in total

First Response

274 ms

Resources Loaded

642 ms

Page Rendered

174 ms

otakod.es screenshot

About Website

Welcome to otakod.es homepage info - get ready to check Otakod best content right away, or after learning these important things about otakod.es

Ariel Dorol, freelance front-end developer and teacher in Paris. I code clean websites, web apps and hybrid mobile apps. Contact me for my availabilities.

Visit otakod.es

Key Findings

We analyzed Otakod.es page load time and found that the first response time was 274 ms and then it took 816 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

otakod.es performance score

96

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

95/100

10%

LCP (Largest Contentful Paint)

Value2.6 s

87/100

25%

SI (Speed Index)

Value1.6 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.6 s

98/100

10%

Network Requests Diagram

otakod.es

274 ms

css

34 ms

styles.css

106 ms

ariel_dorol.jpg

261 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQVIT9d4cw.ttf

27 ms

Our browser made a total of 6 requests to load all elements on the main page. We found that 50% of them (3 requests) were addressed to the original Otakod.es, 33% (2 requests) were made to Fonts.gstatic.com and 17% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (274 ms) belongs to the original domain Otakod.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.5 kB (3%)

Content Size

80.2 kB

After Optimization

77.7 kB

  • HTML
  • Images
  • CSS

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

HTML Optimization

-64%

Potential reduce by 2.5 kB

  • Original 4.0 kB
  • After minification 3.2 kB
  • After compression 1.4 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 715 B, which is 18% 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.5 kB or 64% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 75.2 kB
  • After minification 75.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. Otakod images are well optimized though.

CSS Optimization

-1%

Potential reduce by 16 B

  • Original 1.1 kB
  • After minification 1.1 kB
  • After compression 1.1 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. Otakod.es has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

  • Images
  • CSS

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

Network Requests Diagram

otakod.es

otakod.es

274 ms

css

css

34 ms

styles.css

styles.css

106 ms

ariel_dorol.jpg

ariel_dorol.jpg

261 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQVIT9d4cw.ttf

27 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQVIT9d4cw.ttf

33 ms

Accessibility Review

otakod.es accessibility score

93

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.

Best Practices

otakod.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

SEO Factors

otakod.es SEO score

91

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

otakod.es

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