Tools & Wizards About Us
treemally.com screenshot

Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

Page Load Speed

4.9 sec in total

First Response

664 ms

Resources Loaded

4 sec

Page Rendered

198 ms

treemally.com screenshot

About Website

Welcome to treemally.com homepage info - get ready to check Treemally best content for United States right away, or after learning these important things about treemally.com

Visit treemally.com

Key Findings

We analyzed Treemally.com page load time and found that the first response time was 664 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

treemally.com performance score

0

Network Requests Diagram

treemally.com

664 ms

index.html

1219 ms

main.css

205 ms

activex_activate.js

404 ms

jquery.min.js

25 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 96% of them (47 requests) were addressed to the original Treemally.com, 2% (1 request) were made to Ajax.googleapis.com and 2% (1 request) were made to Crombest.weblog.cafe24.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Treemally.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 71.7 kB (86%)

Content Size

83.9 kB

After Optimization

12.2 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Treemally.com main page is 83.9 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. 20% of websites need less resources to load. CSS take 47.7 kB which makes up the majority of the site volume.

HTML Optimization

-31%

Potential reduce by 128 B

  • Original 412 B
  • After minification 383 B
  • After compression 284 B

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 128 B or 31% of the original size.

JavaScript Optimization

-84%

Potential reduce by 30.1 kB

  • Original 35.8 kB
  • After minification 23.8 kB
  • After compression 5.6 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 30.1 kB or 84% of the original size.

CSS Optimization

-87%

Potential reduce by 41.4 kB

  • Original 47.7 kB
  • After minification 43.1 kB
  • After compression 6.3 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. Treemally.com needs all CSS files to be minified and compressed as it can save up to 41.4 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

47

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

treemally.com

treemally.com

664 ms

index.html

index.html

1219 ms

main.css

main.css

205 ms

activex_activate.js

activex_activate.js

404 ms

jquery.min.js

jquery.min.js

25 ms

jquery.nsp.js

jquery.nsp.js

417 ms

common.js

common.js

425 ms

index_2014_bg.gif

index_2014_bg.gif

206 ms

index_2014_top_01.gif

index_2014_top_01.gif

216 ms

index_2014_02.gif

index_2014_02.gif

206 ms

index_2014_bg2.gif

index_2014_bg2.gif

214 ms

index_2014_04.gif

index_2014_04.gif

816 ms

index_2014_04_2.gif

index_2014_04_2.gif

808 ms

btn_1_on.gif

btn_1_on.gif

408 ms

btn_2_off.gif

btn_2_off.gif

424 ms

index_2014_bg3.gif

index_2014_bg3.gif

427 ms

index_2014_07_1.gif

index_2014_07_1.gif

429 ms

input_bg_id.gif

input_bg_id.gif

609 ms

index_2014_07_2.gif

index_2014_07_2.gif

637 ms

input_bg_pw.gif

input_bg_pw.gif

639 ms

arrow_3.gif

arrow_3.gif

643 ms

index_2014_16.gif

index_2014_16.gif

812 ms

index_2014_08.gif

index_2014_08.gif

850 ms

index_2014_09.gif

index_2014_09.gif

851 ms

index_2014_10.gif

index_2014_10.gif

855 ms

index_2014_11.gif

index_2014_11.gif

1008 ms

index_2014_12.gif

index_2014_12.gif

1015 ms

index_2014_13.gif

index_2014_13.gif

1018 ms

index_2014_14.gif

index_2014_14.gif

1061 ms

index_2014_17.gif

index_2014_17.gif

1062 ms

index_2014_18.gif

index_2014_18.gif

1068 ms

index_2014_19.gif

index_2014_19.gif

1210 ms

index_2014_20.gif

index_2014_20.gif

1216 ms

index_2014_21.gif

index_2014_21.gif

1222 ms

index_2014_22.gif

index_2014_22.gif

1273 ms

index_2014_23.gif

index_2014_23.gif

1274 ms

index_2014_25.gif

index_2014_25.gif

1283 ms

index_2014_27.gif

index_2014_27.gif

1412 ms

arrow_2.gif

arrow_2.gif

1418 ms

index_2014_31.gif

index_2014_31.gif

1427 ms

index_2014_33.gif

index_2014_33.gif

1485 ms

index_2014_35.gif

index_2014_35.gif

1486 ms

weblog.js

weblog.js

624 ms

index_2014_37.gif

index_2014_37.gif

1456 ms

spacer.gif

spacer.gif

1419 ms

index_2014_bt_01.gif

index_2014_bt_01.gif

1424 ms

index_2014_bt_02.gif

index_2014_bt_02.gif

1426 ms

index_2014_bt_03.gif

index_2014_bt_03.gif

1493 ms

index_2014_bt_05.gif

index_2014_bt_05.gif

1299 ms

Accessibility Review

treemally.com accessibility score

33

Accessibility Issues

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

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

treemally.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

treemally.com SEO score

58

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    N/A

  • Encoding

    EUC-KR

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Treemally.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 Treemally.com main page’s claimed encoding is euc-kr. 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

treemally.com

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