Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

Page Load Speed

11.6 sec in total

First Response

1.2 sec

Resources Loaded

10.3 sec

Page Rendered

119 ms

1616dh.com screenshot

About Website

Welcome to 1616dh.com homepage info - get ready to check 1616 Dh best content for South Korea right away, or after learning these important things about 1616dh.com

Visit 1616dh.com

Key Findings

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

1616dh.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value88.9 s

0/100

25%

SI (Speed Index)

Value12.5 s

3/100

10%

TBT (Total Blocking Time)

Value4,750 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.054

98/100

15%

TTI (Time to Interactive)

Value51.0 s

0/100

10%

Network Requests Diagram

1616dh.com

1226 ms

www.1616dh.com

2743 ms

defaultSkin_qtcms.js

510 ms

style.css

1062 ms

skin_def_110815.png

256 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 75% of them (21 requests) were addressed to the original 1616dh.com, 7% (2 requests) were made to Api.114la.com and 4% (1 request) were made to S4.cnzz.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain 1616dh.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 260.8 kB (53%)

Content Size

492.4 kB

After Optimization

231.7 kB

In fact, the total size of 1616dh.com main page is 492.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 5% of websites need less resources to load. Javascripts take 214.3 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 57.8 kB

  • Original 77.9 kB
  • After minification 73.9 kB
  • After compression 20.1 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 57.8 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 2.9 kB

  • Original 144.9 kB
  • After minification 142.0 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. 1616 Dh images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 154.3 kB

  • Original 214.3 kB
  • After minification 183.3 kB
  • After compression 60.0 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 154.3 kB or 72% of the original size.

CSS Optimization

-83%

Potential reduce by 45.8 kB

  • Original 55.4 kB
  • After minification 47.8 kB
  • After compression 9.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. 1616dh.com needs all CSS files to be minified and compressed as it can save up to 45.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (61%)

Requests Now

23

After Optimization

9

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

Accessibility Review

1616dh.com accessibility score

53

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Definition list items are not wrapped in <dl> elements

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

1616dh.com best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

1616dh.com SEO score

80

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

    JA

  • Language Claimed

    N/A

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1616dh.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 1616dh.com main page’s claimed encoding is gbk. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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