Report Summary

  • 59

    Performance

    Renders faster than
    75% of other websites

  • 39

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

fotoya.net

디자인소스 전문 쇼핑몰 - fotoya.net

Page Load Speed

21.5 sec in total

First Response

6.8 sec

Resources Loaded

14.4 sec

Page Rendered

300 ms

fotoya.net screenshot

About Website

Click here to check amazing Fotoya content. Otherwise, check out these important facts you probably never knew about fotoya.net

Visit fotoya.net

Key Findings

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

Performance Metrics

fotoya.net performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value12.9 s

0/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.06

98/100

15%

TTI (Time to Interactive)

Value3.8 s

89/100

10%

Network Requests Diagram

fotoya.net

6757 ms

link.css

683 ms

disomain.css

734 ms

asadalmain.css

636 ms

common.js

1195 ms

Our browser made a total of 210 requests to load all elements on the main page. We found that 27% of them (57 requests) were addressed to the original Fotoya.net, 27% (57 requests) were made to Asadal.com and 27% (56 requests) were made to Image01.asadal.com. The less responsive or slowest element that took the longest time to load (8.5 sec) relates to the external source Image01.asadal.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 733.7 kB (40%)

Content Size

1.8 MB

After Optimization

1.1 MB

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

HTML Optimization

-94%

Potential reduce by 398.8 kB

  • Original 422.4 kB
  • After minification 399.5 kB
  • After compression 23.7 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 398.8 kB or 94% of the original size.

Image Optimization

-22%

Potential reduce by 296.1 kB

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

JavaScript Optimization

-76%

Potential reduce by 26.1 kB

  • Original 34.6 kB
  • After minification 26.1 kB
  • After compression 8.4 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 26.1 kB or 76% of the original size.

CSS Optimization

-83%

Potential reduce by 12.6 kB

  • Original 15.2 kB
  • After minification 13.4 kB
  • After compression 2.6 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. Fotoya.net needs all CSS files to be minified and compressed as it can save up to 12.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 65 (32%)

Requests Now

206

After Optimization

141

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

Accessibility Review

fotoya.net accessibility score

39

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

fotoya.net best practices score

67

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

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

fotoya.net SEO score

62

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

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fotoya.net can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fotoya.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 Fotoya. 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: