Tools & Wizards About Us
yaml.de screenshot

Report Summary

  • 69

    Performance

    Renders faster than
    80% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

yaml.de

YAML CSS Framework — for truly flexible, accessible and responsive websites

Page Load Speed

2.5 sec in total

First Response

396 ms

Resources Loaded

1.8 sec

Page Rendered

222 ms

yaml.de screenshot

About Website

Click here to check amazing YAML content for Russia. Otherwise, check out these important facts you probably never knew about yaml.de

Yet Another Multicolumn Layout (YAML) is a modular CSS framework for truly flexible, accessible and responsive websites.

Visit yaml.de

Key Findings

We analyzed Yaml.de page load time and found that the first response time was 396 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

yaml.de performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

76/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

79/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value600 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value7.9 s

44/100

10%

Network Requests Diagram

yaml.de

396 ms

www.yaml.de

331 ms

css

24 ms

css

41 ms

layout-min.css

214 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 33% of them (10 requests) were addressed to the original Yaml.de, 20% (6 requests) were made to Apis.google.com and 10% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (676 ms) relates to the external source Developers.google.com.

Page Optimization Overview & Recommendations

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

Content Size

348.0 kB

After Optimization

336.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Yaml.de main page is 348.0 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. 45% of websites need less resources to load. Javascripts take 199.9 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 9.7 kB

  • Original 14.3 kB
  • After minification 13.2 kB
  • After compression 4.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 9.7 kB or 68% of the original size.

Image Optimization

-1%

Potential reduce by 1.5 kB

  • Original 133.8 kB
  • After minification 132.3 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. YAML images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 502 B

  • Original 199.9 kB
  • After minification 199.9 kB
  • After compression 199.4 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.

Requests Breakdown

Number of requests can be reduced by 9 (41%)

Requests Now

22

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yaml.de

yaml.de

396 ms

www.yaml.de

www.yaml.de

331 ms

css

css

24 ms

css

css

41 ms

layout-min.css

layout-min.css

214 ms

FB.Share

FB.Share

12 ms

jquery.min.js

jquery.min.js

26 ms

domscripts-min.js

domscripts-min.js

232 ms

ga.js

ga.js

86 ms

gplus-32.png

gplus-32.png

111 ms

widgets.js

widgets.js

104 ms

plusone.js

plusone.js

111 ms

yaml-solo-transparent.png

yaml-solo-transparent.png

120 ms

browser_logos-64.png

browser_logos-64.png

220 ms

HTML5_Logo_128.png

HTML5_Logo_128.png

215 ms

screenshot-thinkintags.jpg

screenshot-thinkintags.jpg

320 ms

screenshot-efa.jpg

screenshot-efa.jpg

321 ms

screenshot-liechtenecker.jpg

screenshot-liechtenecker.jpg

320 ms

font

font

46 ms

font

font

47 ms

font

font

125 ms

__utm.gif

__utm.gif

27 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

10 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

46 ms

fastbutton

fastbutton

42 ms

postmessageRelay

postmessageRelay

36 ms

developers.google.com

developers.google.com

676 ms

3604799710-postmessagerelay.js

3604799710-postmessagerelay.js

12 ms

rpc:shindig_random.js

rpc:shindig_random.js

14 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

5 ms

Accessibility Review

yaml.de accessibility score

90

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.

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

High

Links do not have a discernible name

Best Practices

yaml.de best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

yaml.de 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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yaml.de 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 Yaml.de 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

yaml.de

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