Tools & Wizards About Us
pumddr.com screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

pumddr.com

PC 하드웨어를 사랑한 개발자

Page Load Speed

8.5 sec in total

First Response

1.3 sec

Resources Loaded

7 sec

Page Rendered

273 ms

pumddr.com screenshot

About Website

Visit pumddr.com now to see the best up-to-date Pumddr content and also check out these interesting facts you probably never knew about pumddr.com

한때 스마트폰 개발자였던 하드웨어 매니아 해악사마의 블로그 입니다. ^_^ 문의는 pumddr@naver.com 로 부탁드려요.

Visit pumddr.com

Key Findings

We analyzed Pumddr.com page load time and found that the first response time was 1.3 sec and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster. This domain responded with an error, which can significantly jeopardize Pumddr.com rating and web reputation

Performance Metrics

pumddr.com performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.041

99/100

15%

TTI (Time to Interactive)

Value7.2 s

50/100

10%

Network Requests Diagram

pumddr.com

1303 ms

style.css

1403 ms

style.css

1153 ms

profile.js

1391 ms

jigu-latest.min.js

1638 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Pumddr.com, 43% (40 requests) were made to S1.daumcdn.net and 10% (9 requests) were made to I1.daumcdn.net. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Cfile25.uf.tistory.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 758.9 kB (38%)

Content Size

2.0 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pumddr.com main page is 2.0 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.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 68.0 kB

  • Original 82.1 kB
  • After minification 74.0 kB
  • After compression 14.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 68.0 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 12.7 kB

  • Original 1.1 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. Pumddr images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 166.1 kB

  • Original 293.4 kB
  • After minification 272.3 kB
  • After compression 127.3 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 166.1 kB or 57% of the original size.

CSS Optimization

-91%

Potential reduce by 512.0 kB

  • Original 562.5 kB
  • After minification 534.5 kB
  • After compression 50.5 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. Pumddr.com needs all CSS files to be minified and compressed as it can save up to 512.0 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 57 (63%)

Requests Now

90

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pumddr.com

pumddr.com

1303 ms

style.css

style.css

1403 ms

style.css

style.css

1153 ms

profile.js

profile.js

1391 ms

jigu-latest.min.js

jigu-latest.min.js

1638 ms

T.js

T.js

1170 ms

EAF2.js

EAF2.js

1418 ms

common.js

common.js

1903 ms

gallery.js

gallery.js

1416 ms

flash.js

flash.js

1630 ms

PHON.js

PHON.js

1634 ms

sha256.js

sha256.js

1664 ms

md5.min.js

md5.min.js

1666 ms

swfobject.js

swfobject.js

1867 ms

dialog.css

dialog.css

1868 ms

reset.css

reset.css

1881 ms

tabloid.css

tabloid.css

2407 ms

items.css

items.css

1915 ms

util.css

util.css

2106 ms

tistory-grid-min.css

tistory-grid-min.css

2577 ms

items.js

items.js

2121 ms

menubar.css

menubar.css

1956 ms

633 ms

adsbygoogle.js

adsbygoogle.js

9 ms

searchDragSelection.js

searchDragSelection.js

1781 ms

td.min.js

td.min.js

1440 ms

roosevelt_dk_bt.js

roosevelt_dk_bt.js

930 ms

check.php

check.php

266 ms

266F6B3955D703DF10DD7B

266F6B3955D703DF10DD7B

2133 ms

2550083F5468832603F2C6

2550083F5468832603F2C6

2161 ms

2740DE44544CB2573030EE

2740DE44544CB2573030EE

2362 ms

21313D3C543106B617542B

21313D3C543106B617542B

2339 ms

22689D44542BC9752EC26E

22689D44542BC9752EC26E

1177 ms

2546184054508CDD1D8959

2546184054508CDD1D8959

1377 ms

226E13355427F1B4159009

226E13355427F1B4159009

1720 ms

244EDE3C5423E36E24C42B

244EDE3C5423E36E24C42B

2062 ms

24342A4953ECA5CA1DC5FF

24342A4953ECA5CA1DC5FF

1199 ms

22484B37541570BE03E42C

22484B37541570BE03E42C

1383 ms

27592B4553DEB2930AF193

27592B4553DEB2930AF193

1442 ms

27642F3853CFA02C090014

27642F3853CFA02C090014

1804 ms

tab_top.gif

tab_top.gif

733 ms

count.php

count.php

282 ms

2374DE4154102D0024708F

2374DE4154102D0024708F

1757 ms

2550083F5468832603F2C6

2550083F5468832603F2C6

1765 ms

174C354A4ECFD90407AC68

174C354A4ECFD90407AC68

3418 ms

21313D3C543106B617542B

21313D3C543106B617542B

1446 ms

247F7E3C53F436110E3371

247F7E3C53F436110E3371

1420 ms

2607724A53F9A00B2D36FD

2607724A53F9A00B2D36FD

1886 ms

2740DE44544CB2573030EE

2740DE44544CB2573030EE

1897 ms

2529DF4253E0C71B3394F4

2529DF4253E0C71B3394F4

1385 ms

tab_closed.gif

tab_closed.gif

729 ms

navi_back_active.gif

navi_back_active.gif

729 ms

tab_treed.gif

tab_treed.gif

732 ms

tab_treed_end.gif

tab_treed_end.gif

732 ms

tab_isleaf.gif

tab_isleaf.gif

731 ms

24242743548D9C59271EF3

24242743548D9C59271EF3

1462 ms

233FF94754561BBB2EB773

233FF94754561BBB2EB773

1690 ms

266F6B3955D703DF10DD7B

266F6B3955D703DF10DD7B

1642 ms

menu_div.gif

menu_div.gif

295 ms

searchbar_left.png

searchbar_left.png

251 ms

searchbar_mid.png

searchbar_mid.png

260 ms

txt_search.gif

txt_search.gif

248 ms

btn_search.gif

btn_search.gif

251 ms

searchbar_right.png

searchbar_right.png

242 ms

png.png

png.png

717 ms

g1_1.gif

g1_1.gif

716 ms

g1_0.gif

g1_0.gif

717 ms

rss.gif

rss.gif

461 ms

box_tl.png

box_tl.png

472 ms

box_t.gif

box_t.gif

473 ms

box_tr.png

box_tr.png

474 ms

box_bl.png

box_bl.png

498 ms

box_b.gif

box_b.gif

532 ms

box_br.png

box_br.png

717 ms

stitle_category.gif

stitle_category.gif

708 ms

stitle_notice.gif

stitle_notice.gif

671 ms

stitle_recentpost.gif

stitle_recentpost.gif

673 ms

stitle_recentcomment.gif

stitle_recentcomment.gif

697 ms

ca-pub-8592294207397781.js

ca-pub-8592294207397781.js

162 ms

zrt_lookup.html

zrt_lookup.html

63 ms

show_ads_impl.js

show_ads_impl.js

63 ms

footsteps

footsteps

1698 ms

ads

ads

258 ms

osd.js

osd.js

10 ms

14964197357883055004

14964197357883055004

37 ms

abg.js

abg.js

41 ms

m_js_controller.js

m_js_controller.js

39 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

39 ms

x_button_blue2.png

x_button_blue2.png

6 ms

s

s

20 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

3 ms

print.css

print.css

259 ms

Accessibility Review

pumddr.com accessibility score

65

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.

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

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

SEO Factors

pumddr.com SEO score

86

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

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

    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 Pumddr.com 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 Pumddr.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

pumddr.com

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