Tools & Wizards About Us

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

drumarchive.com

DRUMARCHIVE.COM

Page Load Speed

2.4 sec in total

First Response

330 ms

Resources Loaded

1.8 sec

Page Rendered

266 ms

About Website

Click here to check amazing DRUMARCHIVE content. Otherwise, check out these important facts you probably never knew about drumarchive.com

vintage drums catalogue archive

Visit drumarchive.com

Key Findings

We analyzed Drumarchive.com page load time and found that the first response time was 330 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 45% of websites can load faster.

Performance Metrics

drumarchive.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.0 s

100/100

25%

SI (Speed Index)

Value1.3 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.066

97/100

15%

TTI (Time to Interactive)

Value0.8 s

100/100

10%

Network Requests Diagram

drumarchive.com

330 ms

drumarchive.css

100 ms

SiteLogo.png

195 ms

Ajax.gif

196 ms

Apollo.gif

197 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that all of those requests were addressed to Drumarchive.com and no external sources were called. The less responsive or slowest element that took the longest time to load (702 ms) belongs to the original domain Drumarchive.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 19.2 kB (52%)

Content Size

37.0 kB

After Optimization

17.8 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Drumarchive.com main page is 37.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. 35% of websites need less resources to load. Images take 23.0 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 11.6 kB

  • Original 13.6 kB
  • After minification 13.5 kB
  • After compression 2.0 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 11.6 kB or 85% of the original size.

Image Optimization

-32%

Potential reduce by 7.4 kB

  • Original 23.0 kB
  • After minification 15.6 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. Obviously, DRUMARCHIVE needs image optimization as it can save up to 7.4 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-47%

Potential reduce by 238 B

  • Original 502 B
  • After minification 502 B
  • After compression 264 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. Drumarchive.com needs all CSS files to be minified and compressed as it can save up to 238 B or 47% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

82

After Optimization

82

  • Images
  • CSS

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

Network Requests Diagram

Accessibility Review

drumarchive.com accessibility score

85

Accessibility Issues

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

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

Links do not have a discernible name

Best Practices

drumarchive.com 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

SEO Factors

drumarchive.com SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Drumarchive.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Drumarchive.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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