Tools & Wizards About Us
lenny-face.net screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

lenny-face.net

ᐈ Lenny Face ( ° ͜ʖ °) ✅ 700+ Lenny Faces and Text Faces

Page Load Speed

1.6 sec in total

First Response

126 ms

Resources Loaded

863 ms

Page Rendered

641 ms

lenny-face.net screenshot

About Website

Welcome to lenny-face.net homepage info - get ready to check Lenny Face best content right away, or after learning these important things about lenny-face.net

Unique collection Lenny Face ( ° ͜ʖ °) ( ͡⊙ ͜ʖ ͡⊙), Text Faces ( ͡☉ ͜ʖ ͡☉) ( ͝° ͜ʖ͡°) and Kaomoji ᕦ( ͡° ʖ̯ ͡°)ᕤ ヽ(͡◕ ͜ʖ ͡◕)ﾉ.

Visit lenny-face.net

Key Findings

We analyzed Lenny-face.net page load time and found that the first response time was 126 ms and then it took 1.5 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

lenny-face.net performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

96/100

10%

LCP (Largest Contentful Paint)

Value2.2 s

95/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value2,560 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.041

99/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

www.lenny-face.net

126 ms

style.css

81 ms

js

224 ms

adsbygoogle.js

225 ms

jquery.min.js

49 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 45% of them (9 requests) were addressed to the original Lenny-face.net, 15% (3 requests) were made to Cdnjs.cloudflare.com and 10% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (301 ms) relates to the external source Pagead2.googlesyndication.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 25.7 kB (6%)

Content Size

413.9 kB

After Optimization

388.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lenny-face.net main page is 413.9 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. 40% of websites need less resources to load. Javascripts take 253.5 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 25.4 kB

  • Original 32.6 kB
  • After minification 32.3 kB
  • After compression 7.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. 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 25.4 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 125.2 kB
  • After minification 125.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. Lenny Face images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 187 B

  • Original 253.5 kB
  • After minification 253.4 kB
  • After compression 253.3 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

-3%

Potential reduce by 80 B

  • Original 2.6 kB
  • After minification 2.6 kB
  • After compression 2.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. Lenny-face.net has all CSS files already compressed.

Requests Breakdown

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

Requests Now

19

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lenny Face. 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

www.lenny-face.net

www.lenny-face.net

126 ms

style.css

style.css

81 ms

js

js

224 ms

adsbygoogle.js

adsbygoogle.js

225 ms

jquery.min.js

jquery.min.js

49 ms

jquery.cookie.min.js

jquery.cookie.min.js

59 ms

jquery.sticky.min.js

jquery.sticky.min.js

75 ms

data.js

data.js

75 ms

addthis_widget.js

addthis_widget.js

48 ms

lenny-face.png

lenny-face.png

164 ms

lennyface.png

lennyface.png

165 ms

LennyFacedesktop.png

LennyFacedesktop.png

216 ms

LennyFacemobile.png

LennyFacemobile.png

263 ms

googleplaystore.png

googleplaystore.png

218 ms

chromewebstore.png

chromewebstore.png

217 ms

show_ads_impl.js

show_ads_impl.js

301 ms

zrt_lookup.html

zrt_lookup.html

85 ms

js

js

86 ms

analytics.js

analytics.js

39 ms

collect

collect

14 ms

Accessibility Review

lenny-face.net accessibility score

78

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

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

Image elements do not have [alt] attributes

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

lenny-face.net 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

lenny-face.net SEO score

85

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

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 Lenny-face.net 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 Lenny-face.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

lenny-face.net

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