Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

kuz.com

Kuz Optik Saat | Orjinal Marka Saatler, Güneş Gözlüğü, Çakmak, Kalem

Page Load Speed

6.9 sec in total

First Response

1.2 sec

Resources Loaded

5.4 sec

Page Rendered

404 ms

kuz.com screenshot

About Website

Welcome to kuz.com homepage info - get ready to check Kuz best content for Turkey right away, or after learning these important things about kuz.com

Kuz Optik ve Saat mağazaları 1970 yılından bu yana müşterilerine yenilikçi, güvenilir, müşteri odaklı, profesyonel bir anlayışla hizmet vermektedir.

Visit kuz.com

Key Findings

We analyzed Kuz.com page load time and found that the first response time was 1.2 sec and then it took 5.8 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

kuz.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.7 s

0/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value1,470 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.094

91/100

15%

TTI (Time to Interactive)

Value14.5 s

8/100

10%

Network Requests Diagram

www.kuz.com

1192 ms

jquery-3.6.0.min.js

643 ms

kvkk.cookie.min.js

392 ms

css2

33 ms

all.min.css

533 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 77% of them (27 requests) were addressed to the original Kuz.com, 20% (7 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Kuz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 921.7 kB (35%)

Content Size

2.6 MB

After Optimization

1.7 MB

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

HTML Optimization

-67%

Potential reduce by 98.0 kB

  • Original 145.3 kB
  • After minification 136.1 kB
  • After compression 47.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. 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 98.0 kB or 67% of the original size.

Image Optimization

-0%

Potential reduce by 1.9 kB

  • Original 1.4 MB
  • After minification 1.4 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. Kuz images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 525.5 kB

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

CSS Optimization

-78%

Potential reduce by 296.2 kB

  • Original 377.9 kB
  • After minification 377.9 kB
  • After compression 81.7 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. Kuz.com needs all CSS files to be minified and compressed as it can save up to 296.2 kB or 78% of the original size.

Requests Breakdown

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

Requests Now

23

After Optimization

17

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

Accessibility Review

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

Image elements do not have [alt] attributes

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

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

High

Some elements have a [tabindex] value greater than 0

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

kuz.com best practices score

75

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

Missing source maps for large first-party JavaScript

SEO Factors

kuz.com SEO score

83

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

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 Kuz.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 Kuz.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 Kuz. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: