Tools & Wizards About Us
dgfez.net screenshot

Report Summary

  • 0

    Performance

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

dgfez.net

대구경북경제자유구역청

Page Load Speed

22.5 sec in total

First Response

682 ms

Resources Loaded

20.5 sec

Page Rendered

1.3 sec

dgfez.net screenshot

About Website

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

대구경북경제자유구역청입니다.

Visit dgfez.net

Key Findings

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

Performance Metrics

dgfez.net performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value23.6 s

0/100

10%

TBT (Total Blocking Time)

Value1,540 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.044

99/100

15%

TTI (Time to Interactive)

Value21.8 s

1/100

10%

Network Requests Diagram

dgfez.net

682 ms

www.dgfez.go.kr

1011 ms

www.dgfez.go.kr

5143 ms

jquery-1.11.3.min.js

569 ms

jquery-ui.min.js

1467 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Dgfez.net, 86% (85 requests) were made to Dgfez.go.kr and 10% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (12.1 sec) relates to the external source Dgfez.go.kr.

Page Optimization Overview & Recommendations

Page size can be reduced by 434.8 kB (21%)

Content Size

2.1 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 46.9 kB

  • Original 56.1 kB
  • After minification 51.4 kB
  • After compression 9.2 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 46.9 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 20.3 kB

  • Original 1.6 MB
  • After minification 1.5 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. Dgfez images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 300.8 kB

  • Original 418.1 kB
  • After minification 411.9 kB
  • After compression 117.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 300.8 kB or 72% of the original size.

CSS Optimization

-83%

Potential reduce by 66.9 kB

  • Original 81.0 kB
  • After minification 68.5 kB
  • After compression 14.2 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. Dgfez.net needs all CSS files to be minified and compressed as it can save up to 66.9 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

91

After Optimization

63

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dgfez.net

dgfez.net

682 ms

www.dgfez.go.kr

www.dgfez.go.kr

1011 ms

www.dgfez.go.kr

www.dgfez.go.kr

5143 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

569 ms

jquery-ui.min.js

jquery-ui.min.js

1467 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

662 ms

common.js

common.js

644 ms

main.js

main.js

676 ms

slick.min.js

slick.min.js

919 ms

popup.js

popup.js

759 ms

common.css

common.css

835 ms

layout.css

layout.css

876 ms

main.css

main.css

898 ms

slick.min.css

slick.min.css

950 ms

NotoSansKR.css

NotoSansKR.css

197 ms

ChosunKm.css

ChosunKm.css

211 ms

s-core.css

s-core.css

228 ms

logo.png

logo.png

239 ms

facebook.png

facebook.png

240 ms

youtube2.png

youtube2.png

237 ms

blog2.png

blog2.png

238 ms

linkedin.png

linkedin.png

238 ms

lang_icon.png

lang_icon.png

238 ms

lang_down.png

lang_down.png

431 ms

search.png

search.png

447 ms

search.gif

search.gif

464 ms

search_close.gif

search_close.gif

453 ms

sitemap.png

sitemap.png

449 ms

link_prev.gif

link_prev.gif

430 ms

link_next.gif

link_next.gif

620 ms

mayor_img_230821.png

mayor_img_230821.png

1183 ms

top_mayor_logo.png

top_mayor_logo.png

656 ms

txt_dgfez.png

txt_dgfez.png

660 ms

mayor_tit2.png

mayor_tit2.png

674 ms

map_231219.png

map_231219.png

912 ms

area_img01.jpg

area_img01.jpg

1186 ms

area_img04_230926.jpg

area_img04_230926.jpg

1281 ms

area_img02.jpg

area_img02.jpg

1086 ms

area_img03.jpg

area_img03.jpg

1118 ms

area_img05.jpg

area_img05.jpg

1362 ms

area_img06.jpg

area_img06.jpg

1304 ms

area_img07.jpg

area_img07.jpg

1559 ms

area_img08.jpg

area_img08.jpg

1750 ms

pop_prev.gif

pop_prev.gif

1377 ms

pop_stop.gif

pop_stop.gif

1492 ms

pop_play.png

pop_play.png

1517 ms

pop_next.gif

pop_next.gif

1587 ms

lnk_1704421383.jpg

lnk_1704421383.jpg

1570 ms

lnk_1693800430.jpg

lnk_1693800430.jpg

1914 ms

bod_1704330465.JPG

bod_1704330465.JPG

12144 ms

bod_1703234311.jpg

bod_1703234311.jpg

10080 ms

wa_2024.png

wa_2024.png

1762 ms

notokr-regular.woff

notokr-regular.woff

2235 ms

page.php

page.php

270 ms

notokr-medium.woff

notokr-medium.woff

2086 ms

notokr-light.woff

notokr-light.woff

2131 ms

notokr-bold.woff

notokr-bold.woff

2307 ms

ChosunKm.woff

ChosunKm.woff

9403 ms

visual01.jpg

visual01.jpg

6808 ms

visual02.jpg

visual02.jpg

7413 ms

zVRqzcyf8Om.css

zVRqzcyf8Om.css

15 ms

0_HoU29ShlI.js

0_HoU29ShlI.js

26 ms

Cn_OgNtBsi4.js

Cn_OgNtBsi4.js

26 ms

ru8zNtgW1u3.js

ru8zNtgW1u3.js

56 ms

tJj8um479MM.js

tJj8um479MM.js

54 ms

p55HfXW__mM.js

p55HfXW__mM.js

61 ms

mhWtbsD6qPU.js

mhWtbsD6qPU.js

55 ms

Gnm9vzFr_bN.js

Gnm9vzFr_bN.js

63 ms

408181830_669017135385601_1050854180118668700_n.png

408181830_669017135385601_1050854180118668700_n.png

54 ms

323715707_5766230360130360_985107901741867689_n.jpg

323715707_5766230360130360_985107901741867689_n.jpg

43 ms

ZqKTl42qWXz.js

ZqKTl42qWXz.js

13 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

13 ms

visual03.jpg

visual03.jpg

7753 ms

vis_btn.png

vis_btn.png

6806 ms

cont_bl02.png

cont_bl02.png

6983 ms

cont_bl.png

cont_bl.png

7169 ms

scroll_icon.png

scroll_icon.png

7356 ms

cont01_bg.gif

cont01_bg.gif

7389 ms

cont03_icon01.png

cont03_icon01.png

7381 ms

cont03_icon04.png

cont03_icon04.png

7383 ms

cont03_icon06.png

cont03_icon06.png

7533 ms

cont03_icon03.png

cont03_icon03.png

7558 ms

cont03_icon02.png

cont03_icon02.png

7481 ms

cont03_icon05.png

cont03_icon05.png

7305 ms

mayor_bg.jpg

mayor_bg.jpg

7307 ms

cont02_icon02.png

cont02_icon02.png

7398 ms

board_more.png

board_more.png

7415 ms

movie_bg2.jpg

movie_bg2.jpg

7338 ms

movie_icon.png

movie_icon.png

7466 ms

cont02_icon01.png

cont02_icon01.png

7451 ms

cont02_icon03.png

cont02_icon03.png

7434 ms

cont03_bg.gif

cont03_bg.gif

9359 ms

area_prev.png

area_prev.png

7484 ms

area_next.png

area_next.png

7465 ms

area_line.png

area_line.png

7623 ms

board_on.png

board_on.png

7646 ms

board_bl.gif

board_bl.gif

7632 ms

footer_line.gif

footer_line.gif

7681 ms

top.gif

top.gif

7660 ms

Accessibility Review

dgfez.net accessibility score

94

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Best Practices

dgfez.net 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

dgfez.net 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

    KO

  • Language Claimed

    KO

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dgfez.net can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that Dgfez.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

dgfez.net

Open Graph data is detected on the main page of Dgfez. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: