Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

blog.markum.net

Markum Cloud Blog - Markum Cloud Blog

Page Load Speed

8 sec in total

First Response

2.2 sec

Resources Loaded

5.5 sec

Page Rendered

348 ms

blog.markum.net screenshot

About Website

Visit blog.markum.net now to see the best up-to-date Blog Markum content for Turkey and also check out these interesting facts you probably never knew about blog.markum.net

Cloud dünyasına dair her detayı Markum Cloud Blog'tan takip edeceksiniz!

Visit blog.markum.net

Key Findings

We analyzed Blog.markum.net page load time and found that the first response time was 2.2 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

blog.markum.net performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.6 s

0/100

25%

SI (Speed Index)

Value16.2 s

0/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.061

97/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

blog.markum.net

2158 ms

style.css

544 ms

ddsmoothmenu.css

270 ms

jquery.lightbox-0.5.css

271 ms

jquery-1.4.2.min.js

949 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 52% of them (46 requests) were addressed to the original Blog.markum.net, 14% (12 requests) were made to Static.xx.fbcdn.net and 9% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Blog.markum.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 447.1 kB (56%)

Content Size

796.7 kB

After Optimization

349.6 kB

In fact, the total size of Blog.markum.net main page is 796.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. 45% of websites need less resources to load. Javascripts take 524.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 49.3 kB

  • Original 60.3 kB
  • After minification 57.3 kB
  • After compression 11.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 49.3 kB or 82% of the original size.

Image Optimization

-10%

Potential reduce by 18.9 kB

  • Original 187.0 kB
  • After minification 168.1 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. Blog Markum images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 358.9 kB

  • Original 524.4 kB
  • After minification 497.4 kB
  • After compression 165.5 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 358.9 kB or 68% of the original size.

CSS Optimization

-80%

Potential reduce by 20.0 kB

  • Original 24.9 kB
  • After minification 19.2 kB
  • After compression 5.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. Blog.markum.net needs all CSS files to be minified and compressed as it can save up to 20.0 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (55%)

Requests Now

84

After Optimization

38

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

Accessibility Review

blog.markum.net accessibility score

71

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.

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

Links do not have a discernible name

Best Practices

blog.markum.net best practices score

67

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

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

blog.markum.net SEO score

86

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

    TR

  • Language Claimed

    TR

  • Encoding

    UTF-8

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