Tools & Wizards About Us
blueoreo.tistory.com screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    72% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 85

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

blueoreo.tistory.com

파란오레오

Page Load Speed

9.9 sec in total

First Response

1.6 sec

Resources Loaded

7.8 sec

Page Rendered

526 ms

blueoreo.tistory.com screenshot

About Website

Click here to check amazing Blueoreo Tistory content for South Korea. Otherwise, check out these important facts you probably never knew about blueoreo.tistory.com

파란오레오가 촬영한 사진무단 도용시 법원에서 만나요.

Visit blueoreo.tistory.com

Key Findings

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

Performance Metrics

blueoreo.tistory.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

36/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

2/100

25%

SI (Speed Index)

Value6.9 s

34/100

10%

TBT (Total Blocking Time)

Value170 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

blueoreo.tistory.com

1568 ms

style.css

963 ms

wcslog.js

14 ms

FN_Script.js

970 ms

FindNemoData.js

656 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Blueoreo.tistory.com, 51% (44 requests) were made to S1.daumcdn.net and 16% (14 requests) were made to I1.daumcdn.net. The less responsive or slowest element that took the longest time to load (4.3 sec) relates to the external source Cfile3.uf.tistory.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 981.0 kB (39%)

Content Size

2.5 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blueoreo.tistory.com main page is 2.5 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.3 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 172.0 kB

  • Original 191.0 kB
  • After minification 176.5 kB
  • After compression 19.0 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 172.0 kB or 90% of the original size.

Image Optimization

-1%

Potential reduce by 16.8 kB

  • Original 1.3 MB
  • After minification 1.3 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. Blueoreo Tistory images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 286.9 kB

  • Original 416.3 kB
  • After minification 394.6 kB
  • After compression 129.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 286.9 kB or 69% of the original size.

CSS Optimization

-91%

Potential reduce by 505.3 kB

  • Original 555.0 kB
  • After minification 529.2 kB
  • After compression 49.8 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. Blueoreo.tistory.com needs all CSS files to be minified and compressed as it can save up to 505.3 kB or 91% of the original size.

Requests Breakdown

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

Requests Now

71

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blueoreo.tistory.com

blueoreo.tistory.com

1568 ms

style.css

style.css

963 ms

wcslog.js

wcslog.js

14 ms

FN_Script.js

FN_Script.js

970 ms

FindNemoData.js

FindNemoData.js

656 ms

lightbox.min.css

lightbox.min.css

971 ms

style.css

style.css

971 ms

profile.js

profile.js

975 ms

jigu-latest.min.js

jigu-latest.min.js

1455 ms

T.js

T.js

1182 ms

EAF2.js

EAF2.js

1421 ms

common.js

common.js

1657 ms

gallery.js

gallery.js

1193 ms

flash.js

flash.js

1213 ms

PHON.js

PHON.js

1407 ms

sha256.js

sha256.js

1424 ms

md5.min.js

md5.min.js

1458 ms

swfobject.js

swfobject.js

1631 ms

dialog.css

dialog.css

1649 ms

reset.css

reset.css

1661 ms

tabloid.css

tabloid.css

1928 ms

items.css

items.css

1689 ms

util.css

util.css

1854 ms

tistory-grid-min.css

tistory-grid-min.css

2579 ms

items.js

items.js

1883 ms

menubar.css

menubar.css

1884 ms

functions.js

functions.js

1235 ms

searchDragSelection.js

searchDragSelection.js

1377 ms

lightbox.min.js

lightbox.min.js

1413 ms

td.min.js

td.min.js

815 ms

roosevelt_dk_bt.js

roosevelt_dk_bt.js

6 ms

m

m

539 ms

analytics.js

analytics.js

24 ms

collect

collect

24 ms

check.php

check.php

293 ms

223B034353CB70FB06F0BF

223B034353CB70FB06F0BF

4303 ms

264FB03B56E41A1832A2BA

264FB03B56E41A1832A2BA

1885 ms

234F534156E40CB62A87A8

234F534156E40CB62A87A8

1846 ms

2365274156E4084404F581

2365274156E4084404F581

3037 ms

2325FF3E56E406A908CABC

2325FF3E56E406A908CABC

3513 ms

ico_twitter.gif

ico_twitter.gif

26 ms

2121494256E3FF381F977E

2121494256E3FF381F977E

2747 ms

2121494256E3FF381F977E

2121494256E3FF381F977E

2446 ms

count.php

count.php

548 ms

24067C3D56E402E721FA98

24067C3D56E402E721FA98

3517 ms

2325FF3E56E406A908CABC

2325FF3E56E406A908CABC

1933 ms

24067C3D56E402E721FA98

24067C3D56E402E721FA98

1950 ms

2365274156E4084404F581

2365274156E4084404F581

1844 ms

264FB03B56E41A1832A2BA

264FB03B56E41A1832A2BA

1945 ms

close.png

close.png

243 ms

loading.gif

loading.gif

480 ms

prev.png

prev.png

243 ms

next.png

next.png

245 ms

btn_search.gif

btn_search.gif

248 ms

icon_rss.gif

icon_rss.gif

250 ms

234F534156E40CB62A87A8

234F534156E40CB62A87A8

1436 ms

tab_top.gif

tab_top.gif

20 ms

new_ico_5.gif

new_ico_5.gif

21 ms

tab_closed.gif

tab_closed.gif

22 ms

navi_back_active.gif

navi_back_active.gif

21 ms

tab_treed.gif

tab_treed.gif

21 ms

tab_treed_end.gif

tab_treed_end.gif

21 ms

tab_isleaf.gif

tab_isleaf.gif

22 ms

t_logo.png

t_logo.png

22 ms

bg_header.gif

bg_header.gif

453 ms

bg_sidebar1.gif

bg_sidebar1.gif

457 ms

bg_sidebar.gif

bg_sidebar.gif

470 ms

bg_headermenu_01tag.gif

bg_headermenu_01tag.gif

469 ms

bg_headermenu_02li.gif

bg_headermenu_02li.gif

459 ms

bg_headermenu_06write.gif

bg_headermenu_06write.gif

695 ms

bg_sidebar2.gif

bg_sidebar2.gif

696 ms

bg_comment_bg1.png

bg_comment_bg1.png

43 ms

bg_comment_bg2.png

bg_comment_bg2.png

43 ms

bg_sidebar_b2.png

bg_sidebar_b2.png

44 ms

bt_plus.gif

bt_plus.gif

43 ms

title_category.gif

title_category.gif

651 ms

title_comment.gif

title_comment.gif

636 ms

bul_sidebar.gif

bul_sidebar.gif

641 ms

title_calendar.gif

title_calendar.gif

645 ms

bg_calendar_today.gif

bg_calendar_today.gif

854 ms

m

m

406 ms

collect

collect

9 ms

jquery.min.js

jquery.min.js

86 ms

box_d01_logout.png

box_d01_logout.png

8 ms

footsteps

footsteps

1069 ms

223B034353CB70FB06F0BF

223B034353CB70FB06F0BF

1629 ms

Accessibility Review

blueoreo.tistory.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

blueoreo.tistory.com best practices score

85

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

blueoreo.tistory.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 Blueoreo.tistory.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 Blueoreo.tistory.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

blueoreo.tistory.com

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