Report Summary

  • 54

    Performance

    Renders faster than
    72% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

tympanus.net

Codrops | Creative front-end resources and inspiration for web professionals

Page Load Speed

161 ms in total

First Response

13 ms

Resources Loaded

66 ms

Page Rendered

82 ms

tympanus.net screenshot

About Website

Welcome to tympanus.net homepage info - get ready to check Tympanus best content for India right away, or after learning these important things about tympanus.net

Creative front-end resources and inspiration for web professionals

Visit tympanus.net

Key Findings

We analyzed Tympanus.net page load time and found that the first response time was 13 ms and then it took 148 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

tympanus.net performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value460 ms

62/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.9 s

54/100

10%

Network Requests Diagram

tympanus.net

13 ms

css

25 ms

style.css

6 ms

Tympanus_GettingMakeover.png

6 ms

GCfZZhEBktKQec0okJ7kUw.ttf

7 ms

Our browser made a total of 5 requests to load all elements on the main page. We found that 60% of them (3 requests) were addressed to the original Tympanus.net, 20% (1 request) were made to Fonts.googleapis.com and 20% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (25 ms) relates to the external source Fonts.googleapis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.0 kB (2%)

Content Size

154.7 kB

After Optimization

151.7 kB

In fact, the total size of Tympanus.net main page is 154.7 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. Images take 152.3 kB which makes up the majority of the site volume.

HTML Optimization

-52%

Potential reduce by 567 B

  • Original 1.1 kB
  • After minification 953 B
  • After compression 519 B

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 133 B, which is 12% 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 567 B or 52% of the original size.

Image Optimization

-1%

Potential reduce by 1.8 kB

  • Original 152.3 kB
  • After minification 150.5 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. Tympanus images are well optimized though.

CSS Optimization

-50%

Potential reduce by 679 B

  • Original 1.3 kB
  • After minification 1.1 kB
  • After compression 667 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. Tympanus.net needs all CSS files to be minified and compressed as it can save up to 679 B or 50% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

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

Accessibility Review

tympanus.net accessibility score

73

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

tympanus.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

tympanus.net SEO score

93

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

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 Tympanus.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 Tympanus.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 Tympanus. 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: