Tools & Wizards About Us
ozkarakus.com screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

ozkarakus.com

Özkarakuş | Anasayfa

Page Load Speed

4.9 sec in total

First Response

439 ms

Resources Loaded

4.2 sec

Page Rendered

273 ms

ozkarakus.com screenshot

About Website

Welcome to ozkarakus.com homepage info - get ready to check Ozkarakus best content right away, or after learning these important things about ozkarakus.com

Özkarakuş | Anasayfa

Visit ozkarakus.com

Key Findings

We analyzed Ozkarakus.com page load time and found that the first response time was 439 ms and then it took 4.5 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

ozkarakus.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value7.4 s

27/100

10%

TBT (Total Blocking Time)

Value340 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0.101

89/100

15%

TTI (Time to Interactive)

Value10.0 s

26/100

10%

Network Requests Diagram

ozkarakus.com

439 ms

ozkarakus.com

559 ms

www.ozkarakus.com

886 ms

api.js

33 ms

material-design-iconic-font.min.css

401 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 86% of them (56 requests) were addressed to the original Ozkarakus.com, 6% (4 requests) were made to Maps.googleapis.com and 3% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Ozkarakus.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 354.3 kB (27%)

Content Size

1.3 MB

After Optimization

936.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 33.9 kB

  • Original 39.8 kB
  • After minification 27.0 kB
  • After compression 5.9 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 12.9 kB, which is 32% 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 33.9 kB or 85% of the original size.

Image Optimization

-8%

Potential reduce by 52.6 kB

  • Original 633.1 kB
  • After minification 580.5 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. Ozkarakus images are well optimized though.

JavaScript Optimization

-42%

Potential reduce by 197.3 kB

  • Original 474.9 kB
  • After minification 474.9 kB
  • After compression 277.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 197.3 kB or 42% of the original size.

CSS Optimization

-49%

Potential reduce by 70.4 kB

  • Original 143.3 kB
  • After minification 143.3 kB
  • After compression 72.9 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. Ozkarakus.com needs all CSS files to be minified and compressed as it can save up to 70.4 kB or 49% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (68%)

Requests Now

60

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ozkarakus.com

ozkarakus.com

439 ms

ozkarakus.com

ozkarakus.com

559 ms

www.ozkarakus.com

www.ozkarakus.com

886 ms

api.js

api.js

33 ms

material-design-iconic-font.min.css

material-design-iconic-font.min.css

401 ms

font-awesome.min.css

font-awesome.min.css

537 ms

animate.css

animate.css

538 ms

owl.carousel.min.css

owl.carousel.min.css

429 ms

slick.css

slick.css

431 ms

meanmenu.min.css

meanmenu.min.css

433 ms

jquery-ui.css

jquery-ui.css

535 ms

nice-select.css

nice-select.css

573 ms

easyzoom.css

easyzoom.css

575 ms

venobox.css

venobox.css

721 ms

bootstrap.min.css

bootstrap.min.css

934 ms

style.css

style.css

939 ms

responsive.css

responsive.css

671 ms

modernizr-2.8.3.min.js

modernizr-2.8.3.min.js

857 ms

cookieconsent.min.css

cookieconsent.min.css

44 ms

cookieconsent.min.js

cookieconsent.min.js

90 ms

jquery-1.12.4.min.js

jquery-1.12.4.min.js

1004 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

805 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

1008 ms

waypoints.min.js

waypoints.min.js

943 ms

owl.carousel.min.js

owl.carousel.min.js

1142 ms

slick.min.js

slick.min.js

1067 ms

jquery.meanmenu.min.js

jquery.meanmenu.min.js

1069 ms

instafeed.min.js

instafeed.min.js

1073 ms

jquery.countdown.min.js

jquery.countdown.min.js

1147 ms

jquery.counterup.min.js

jquery.counterup.min.js

1152 ms

jquery.scrollUp.min.js

jquery.scrollUp.min.js

1200 ms

jquery-ui.js

jquery-ui.js

1507 ms

jquery.nice-select.min.js

jquery.nice-select.min.js

1207 ms

easyzoom.min.js

easyzoom.min.js

1284 ms

wow.min.js

wow.min.js

1291 ms

venobox.min.js

venobox.min.js

1296 ms

popper.min.js

popper.min.js

1334 ms

bootstrap.min.js

bootstrap.min.js

1507 ms

plugins.js

plugins.js

1427 ms

main.js

main.js

1434 ms

recaptcha__en.js

recaptcha__en.js

21 ms

css.css

css.css

505 ms

tr.png

tr.png

174 ms

en.png

en.png

176 ms

logo.png

logo.png

176 ms

d4fae7a21d883a67ec803042ea50c8.png

d4fae7a21d883a67ec803042ea50c8.png

176 ms

title-icon.png

title-icon.png

174 ms

0

0

176 ms

100x00x40-kare-buat-eski-tip.png

100x00x40-kare-buat-eski-tip.png

271 ms

120x120x40-kare-buat-eski-tip.png

120x120x40-kare-buat-eski-tip.png

271 ms

0db493c3be0d27cd0ae3913798f692.png

0db493c3be0d27cd0ae3913798f692.png

287 ms

0336201ca8f3aee73438c1f20dacc0.png

0336201ca8f3aee73438c1f20dacc0.png

289 ms

ff4cbdb97d816ef60a1be73225cf1a.png

ff4cbdb97d816ef60a1be73225cf1a.png

290 ms

d3c13ecd152b1b12c5e72b6dcb8fe2.png

d3c13ecd152b1b12c5e72b6dcb8fe2.png

294 ms

ef075cd37943735f40e46e90552ffc.png

ef075cd37943735f40e46e90552ffc.png

405 ms

ee082bb9a8c84a3cd7af4fb6afb3c7.png

ee082bb9a8c84a3cd7af4fb6afb3c7.png

404 ms

ac0c3800108449d9b921ff60310275.png

ac0c3800108449d9b921ff60310275.png

430 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

402 ms

embed

embed

165 ms

slider1.jpg

slider1.jpg

692 ms

slider2.jpg

slider2.jpg

658 ms

js

js

36 ms

geometry.js

geometry.js

5 ms

search.js

search.js

9 ms

main.js

main.js

11 ms

Accessibility Review

ozkarakus.com accessibility score

94

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

ozkarakus.com SEO score

90

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

    TR

  • Language Claimed

    TR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ozkarakus.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 Ozkarakus.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

ozkarakus.com

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