Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

maranki.com

Prof. Dr. Ahmet Maranki Resmi Web Sitesi

Page Load Speed

8.4 sec in total

First Response

339 ms

Resources Loaded

6.7 sec

Page Rendered

1.3 sec

About Website

Click here to check amazing Maranki content for Turkey. Otherwise, check out these important facts you probably never knew about maranki.com

Bitkilerin Efendisi Lokman Hekim Ahmet Maranki Hocadan Şifalı Bitkiler, Şifalı Kürler ve Sağlıklı Yaşam Hakkında Tüm Detaylar Sizler İçin Bu Sitede.

Visit maranki.com

Key Findings

We analyzed Maranki.com page load time and found that the first response time was 339 ms and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

maranki.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value15.3 s

1/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.488

17/100

15%

TTI (Time to Interactive)

Value20.7 s

2/100

10%

Network Requests Diagram

maranki.com

339 ms

www.maranki.com

637 ms

style.min.css

470 ms

theme.min.css

24 ms

styles.css

25 ms

Our browser made a total of 135 requests to load all elements on the main page. We found that 70% of them (95 requests) were addressed to the original Maranki.com, 11% (15 requests) were made to Foto.haberler.com and 11% (15 requests) were made to Haberler.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Maranki.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.3 MB (26%)

Content Size

12.8 MB

After Optimization

9.5 MB

In fact, the total size of Maranki.com main page is 12.8 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. 65% of websites need less resources to load. Images take 12.3 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 186.5 kB

  • Original 211.5 kB
  • After minification 190.2 kB
  • After compression 25.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 186.5 kB or 88% of the original size.

Image Optimization

-25%

Potential reduce by 3.1 MB

  • Original 12.3 MB
  • After minification 9.2 MB

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, Maranki needs image optimization as it can save up to 3.1 MB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 363 B

  • Original 206.6 kB
  • After minification 206.6 kB
  • After compression 206.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-8%

Potential reduce by 2.8 kB

  • Original 36.1 kB
  • After minification 36.1 kB
  • After compression 33.4 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. Maranki.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (26%)

Requests Now

109

After Optimization

81

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

Accessibility Review

maranki.com accessibility score

79

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

[id] attributes on active, focusable elements are not unique

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

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

maranki.com SEO score

91

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

High

Tap targets are not sized appropriately

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

Open Graph data is detected on the main page of Maranki. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: