Tools & Wizards About Us
intono.de screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

intono.de

intono Records – intono Records

Page Load Speed

6 sec in total

First Response

1.1 sec

Resources Loaded

4.8 sec

Page Rendered

89 ms

intono.de screenshot

About Website

Welcome to intono.de homepage info - get ready to check Intono best content right away, or after learning these important things about intono.de

Gegründet, um von Hannover aus den Globus zu rocken, bietet intono records Musikern eine Plattform, ihre Musik unter die Leute zu bringen. Unsere Schaltzentrale ist das im Herzen von Hannover gelegene...

Visit intono.de

Key Findings

We analyzed Intono.de page load time and found that the first response time was 1.1 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

intono.de performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.225

55/100

15%

TTI (Time to Interactive)

Value6.0 s

64/100

10%

Network Requests Diagram

www.intono.de

1107 ms

jquery.min.js

303 ms

jquery-migrate.min.js

396 ms

cssua.js

205 ms

fusion-animations.js

222 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (84%)

Content Size

1.6 MB

After Optimization

247.8 kB

  • HTML
  • Images

In fact, the total size of Intono.de main page is 1.6 MB. 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. HTML takes 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 1.3 MB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 216.5 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 1.3 MB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 31.3 kB
  • After minification 31.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. Intono images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 48 (94%)

Requests Now

51

After Optimization

3

  • Images
  • JavaScript

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

Network Requests Diagram

www.intono.de

www.intono.de

1107 ms

jquery.min.js

jquery.min.js

303 ms

jquery-migrate.min.js

jquery-migrate.min.js

396 ms

cssua.js

cssua.js

205 ms

fusion-animations.js

fusion-animations.js

222 ms

modernizr.js

modernizr.js

229 ms

fusion.js

fusion.js

227 ms

swiper.js

swiper.js

433 ms

bootstrap.transition.js

bootstrap.transition.js

325 ms

bootstrap.tooltip.js

bootstrap.tooltip.js

326 ms

jquery.requestAnimationFrame.js

jquery.requestAnimationFrame.js

325 ms

jquery.easing.js

jquery.easing.js

331 ms

jquery.fitvids.js

jquery.fitvids.js

330 ms

jquery.flexslider.js

jquery.flexslider.js

430 ms

jquery.ilightbox.js

jquery.ilightbox.js

435 ms

jquery.mousewheel.js

jquery.mousewheel.js

428 ms

jquery.placeholder.js

jquery.placeholder.js

435 ms

jquery.fade.js

jquery.fade.js

440 ms

fusion-parallax.js

fusion-parallax.js

532 ms

fusion-video-general.js

fusion-video-general.js

534 ms

fusion-video-bg.js

fusion-video-bg.js

535 ms

fusion-lightbox.js

fusion-lightbox.js

537 ms

fusion-tooltip.js

fusion-tooltip.js

538 ms

fusion-sharing-box.js

fusion-sharing-box.js

538 ms

jquery.sticky-kit.js

jquery.sticky-kit.js

635 ms

fusion-youtube.js

fusion-youtube.js

636 ms

vimeoPlayer.js

vimeoPlayer.js

639 ms

avada-general-footer.js

avada-general-footer.js

640 ms

avada-quantity.js

avada-quantity.js

641 ms

avada-crossfade-images.js

avada-crossfade-images.js

642 ms

avada-select.js

avada-select.js

738 ms

avada-live-search.js

avada-live-search.js

738 ms

fusion-alert.js

fusion-alert.js

741 ms

awb-off-canvas.js

awb-off-canvas.js

743 ms

fusion-flexslider.js

fusion-flexslider.js

743 ms

awb-background-slider.js

awb-background-slider.js

743 ms

fusion-container.js

fusion-container.js

841 ms

avada-drop-down.js

avada-drop-down.js

648 ms

avada-to-top.js

avada-to-top.js

649 ms

avada-header.js

avada-header.js

651 ms

avada-menu.js

avada-menu.js

634 ms

bootstrap.scrollspy.js

bootstrap.scrollspy.js

629 ms

avada-scrollspy.js

avada-scrollspy.js

693 ms

fusion-responsive-typography.js

fusion-responsive-typography.js

630 ms

fusion-scroll-to-anchor.js

fusion-scroll-to-anchor.js

630 ms

fusion-general-global.js

fusion-general-global.js

632 ms

fusion-video.js

fusion-video.js

628 ms

fusion-column.js

fusion-column.js

628 ms

borlabs-cookie.min.js

borlabs-cookie.min.js

629 ms

lazyload.min.js

lazyload.min.js

627 ms

awb-icons.woff

awb-icons.woff

656 ms

logo-2023-08-03.png

logo-2023-08-03.png

724 ms

borlabs-cookie-icon-dynamic.svg

borlabs-cookie-icon-dynamic.svg

650 ms

Accessibility Review

intono.de accessibility score

98

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

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

SEO Factors

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

    DE

  • Encoding

    UTF-8

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

intono.de

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