Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

fizy.com

fizy - Digital Müzik ve Video Platformu

Page Load Speed

22 sec in total

First Response

379 ms

Resources Loaded

20.9 sec

Page Rendered

748 ms

fizy.com screenshot

About Website

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

fizy milyonlarca şarkı, video klip, onlarca radyo kanalı ve fazlasına ulaşmanı sağlayan dijital müzik platformudur. fizy’i keşfe çıkmak için hemen tıkla.

Visit fizy.com

Key Findings

We analyzed Fizy.com page load time and found that the first response time was 379 ms and then it took 21.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

fizy.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value21.4 s

0/100

25%

SI (Speed Index)

Value4.5 s

72/100

10%

TBT (Total Blocking Time)

Value2,470 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.044

99/100

15%

TTI (Time to Interactive)

Value28.4 s

0/100

10%

Network Requests Diagram

fizy.com

379 ms

fizy.com

529 ms

ruxitagentjs_ICANVfhqru_10287240325103108.js

6405 ms

7.style.css

483 ms

bluebird.min.js

502 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 75% of them (49 requests) were addressed to the original Fizy.com, 6% (4 requests) were made to Googletagmanager.com and 6% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (13.4 sec) belongs to the original domain Fizy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 386.1 kB (15%)

Content Size

2.6 MB

After Optimization

2.2 MB

In fact, the total size of Fizy.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. 60% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 43.9 kB

  • Original 56.8 kB
  • After minification 55.1 kB
  • After compression 12.8 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 43.9 kB or 77% of the original size.

Image Optimization

-12%

Potential reduce by 256.9 kB

  • Original 2.2 MB
  • After minification 1.9 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, Fizy needs image optimization as it can save up to 256.9 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-25%

Potential reduce by 85.3 kB

  • Original 338.0 kB
  • After minification 338.0 kB
  • After compression 252.8 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 85.3 kB or 25% of the original size.

CSS Optimization

-0%

Potential reduce by 41 B

  • Original 14.1 kB
  • After minification 14.1 kB
  • After compression 14.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. Fizy.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

57

After Optimization

41

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

Accessibility Review

fizy.com accessibility score

72

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Heading elements are not in a sequentially-descending order

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

fizy.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

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