Tools & Wizards About Us
markant.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

markant.com

Markant Handels- und Industriewaren-Vermittlungs AG: Global

Page Load Speed

2.5 sec in total

First Response

717 ms

Resources Loaded

1.6 sec

Page Rendered

170 ms

markant.com screenshot

About Website

Welcome to markant.com homepage info - get ready to check Markant best content for Germany right away, or after learning these important things about markant.com

Wir sind der verlässliche Partner für Lieferanten und Händler. Prozessoptimierung, Bezahlsysteme, Datenqualität, Planungssicherheit – mach es markant!

Visit markant.com

Key Findings

We analyzed Markant.com page load time and found that the first response time was 717 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

markant.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value1,000 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.359

30/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

markant.com

717 ms

dscss_2031.css

281 ms

prototype.js

463 ms

scriptaculous.js

284 ms

jquery.js

483 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 91% of them (31 requests) were addressed to the original Markant.com, 6% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (717 ms) belongs to the original domain Markant.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 468.1 kB (64%)

Content Size

733.7 kB

After Optimization

265.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Markant.com main page is 733.7 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. 30% of websites need less resources to load. Javascripts take 510.9 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 14.4 kB

  • Original 18.8 kB
  • After minification 15.6 kB
  • After compression 4.3 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. This page needs HTML code to be minified as it can gain 3.2 kB, which is 17% 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 14.4 kB or 77% of the original size.

Image Optimization

-7%

Potential reduce by 12.2 kB

  • Original 164.5 kB
  • After minification 152.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. Markant images are well optimized though.

JavaScript Optimization

-80%

Potential reduce by 408.0 kB

  • Original 510.9 kB
  • After minification 368.1 kB
  • After compression 103.0 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 408.0 kB or 80% of the original size.

CSS Optimization

-85%

Potential reduce by 33.5 kB

  • Original 39.5 kB
  • After minification 29.0 kB
  • After compression 6.0 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. Markant.com needs all CSS files to be minified and compressed as it can save up to 33.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (73%)

Requests Now

33

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

markant.com

markant.com

717 ms

dscss_2031.css

dscss_2031.css

281 ms

prototype.js

prototype.js

463 ms

scriptaculous.js

scriptaculous.js

284 ms

jquery.js

jquery.js

483 ms

jquery.fancybox-1.3.1.css

jquery.fancybox-1.3.1.css

188 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

272 ms

jquery.fancybox-1.3.1.pack.js

jquery.fancybox-1.3.1.pack.js

373 ms

jquery.tooltip.min.js

jquery.tooltip.min.js

290 ms

flexslider.css

flexslider.css

375 ms

custom.css

custom.css

382 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

5 ms

jquery.flexslider.js

jquery.flexslider.js

482 ms

bg.jpg

bg.jpg

284 ms

logo.png

logo.png

285 ms

bu_suche.gif

bu_suche.gif

287 ms

blank.gif

blank.gif

356 ms

no_flash.jpg

no_flash.jpg

459 ms

doppelpfeile.gif

doppelpfeile.gif

367 ms

logo_sw.jpg

logo_sw.jpg

366 ms

mnet_login.png

mnet_login.png

465 ms

pfeil.gif

pfeil.gif

379 ms

builder.js

builder.js

169 ms

effects.js

effects.js

190 ms

dragdrop.js

dragdrop.js

194 ms

slider.js

slider.js

197 ms

controls.js

controls.js

265 ms

print.css

print.css

98 ms

bg_head6.png

bg_head6.png

282 ms

bg_suche.gif

bg_suche.gif

95 ms

bg_content.png

bg_content.png

96 ms

bg_foot3.png

bg_foot3.png

97 ms

ga.js

ga.js

24 ms

__utm.gif

__utm.gif

23 ms

Accessibility Review

markant.com accessibility score

75

Accessibility Issues

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

Buttons do not have an accessible name

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

markant.com best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

markant.com SEO score

89

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

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

markant.com

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