Tools & Wizards About Us
webstory.my screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

webstory.my

diary writing :: from paper diary to digital diary

Page Load Speed

7.5 sec in total

First Response

681 ms

Resources Loaded

6 sec

Page Rendered

849 ms

webstory.my screenshot

About Website

Welcome to webstory.my homepage info - get ready to check Webstory best content right away, or after learning these important things about webstory.my

personal diary and digital journal software

Visit webstory.my

Key Findings

We analyzed Webstory.my page load time and found that the first response time was 681 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

webstory.my performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value210 ms

88/100

30%

CLS (Cumulative Layout Shift)

Value0.134

80/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

Network Requests Diagram

webstory.my

681 ms

style.css

294 ms

adminbar.css

295 ms

bbpress.css

297 ms

base.css

442 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 31% of them (26 requests) were addressed to the original Webstory.my, 14% (12 requests) were made to Static.xx.fbcdn.net and 10% (8 requests) were made to Webstory.self.my. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Webstory.self.my.

Page Optimization Overview & Recommendations

Page size can be reduced by 500.8 kB (47%)

Content Size

1.1 MB

After Optimization

558.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Webstory.my main page is 1.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. 55% of websites need less resources to load. Images take 406.9 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 102.7 kB

  • Original 119.1 kB
  • After minification 117.5 kB
  • After compression 16.4 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 102.7 kB or 86% of the original size.

Image Optimization

-8%

Potential reduce by 33.6 kB

  • Original 406.9 kB
  • After minification 373.4 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. Webstory images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 246.2 kB

  • Original 390.4 kB
  • After minification 337.6 kB
  • After compression 144.2 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 246.2 kB or 63% of the original size.

CSS Optimization

-83%

Potential reduce by 118.3 kB

  • Original 142.6 kB
  • After minification 111.1 kB
  • After compression 24.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. Webstory.my needs all CSS files to be minified and compressed as it can save up to 118.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (58%)

Requests Now

81

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

webstory.my

webstory.my

681 ms

style.css

style.css

294 ms

adminbar.css

adminbar.css

295 ms

bbpress.css

bbpress.css

297 ms

base.css

base.css

442 ms

bp-default.css

bp-default.css

447 ms

bp-css.css

bp-css.css

433 ms

adminbar.css

adminbar.css

444 ms

ga-async.css

ga-async.css

446 ms

shr-custom-sprite.css

shr-custom-sprite.css

586 ms

prototype.js

prototype.js

1346 ms

wp-scriptaculous.js

wp-scriptaculous.js

2236 ms

effects.js

effects.js

2334 ms

lightbox-resize.js

lightbox-resize.js

448 ms

anywhere.js

anywhere.js

5 ms

jquery.js

jquery.js

3217 ms

drop_down.js

drop_down.js

579 ms

modernizr.js

modernizr.js

586 ms

comment-reply.js

comment-reply.js

2238 ms

shareaholic-perf.min.js

shareaholic-perf.min.js

585 ms

recipe.js

recipe.js

7 ms

widgets.js

widgets.js

2 ms

sexy-bookmarks-public.min.js

sexy-bookmarks-public.min.js

306 ms

ga.js

ga.js

5 ms

shareaholic_analytics.js

shareaholic_analytics.js

44 ms

lightbox.css

lightbox.css

147 ms

__utm.gif

__utm.gif

25 ms

WebStoryLogo32.png

WebStoryLogo32.png

1058 ms

fb66af0e38def9ea6fde936831a69637

fb66af0e38def9ea6fde936831a69637

54 ms

CSWebStoryBig.jpg

CSWebStoryBig.jpg

639 ms

DownloadFree.png

DownloadFree.png

473 ms

Download-For-Free.png

Download-For-Free.png

418 ms

supported3.png

supported3.png

816 ms

thumb_WP-Editor.png

thumb_WP-Editor.png

418 ms

thumb_ArticleEditor.png

thumb_ArticleEditor.png

900 ms

5e9eff2bcef67e708dff93ae3273646e-bpthumb.jpg

5e9eff2bcef67e708dff93ae3273646e-bpthumb.jpg

554 ms

icon_smile.gif

icon_smile.gif

555 ms

3d57a0b6ee5402c1ff680716e9d434d0-bpthumb.jpg

3d57a0b6ee5402c1ff680716e9d434d0-bpthumb.jpg

617 ms

da2fdcb34b3b9419c4961fbf7a2545b9-bpthumb.jpg

da2fdcb34b3b9419c4961fbf7a2545b9-bpthumb.jpg

699 ms

3263009fd26008225e643443a882292d

3263009fd26008225e643443a882292d

74 ms

d7294a77feef861a45efca60b1ff636c

d7294a77feef861a45efca60b1ff636c

134 ms

1ef3c99f68dc927cbd4ff3f26d33e87f

1ef3c99f68dc927cbd4ff3f26d33e87f

135 ms

hbpix

hbpix

29 ms

wp-loader.js

wp-loader.js

10 ms

ga.js

ga.js

5 ms

header-notifications.js

header-notifications.js

11 ms

sharing-shr.png

sharing-shr.png

1125 ms

shr-custom-sprite.png

shr-custom-sprite.png

1693 ms

admin-menu-arrow.gif

admin-menu-arrow.gif

552 ms

all.js

all.js

39 ms

xdmStore.js

xdmStore.js

67 ms

analytics_frame.html

analytics_frame.html

85 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

76 ms

163 ms

remote.html

remote.html

31 ms

xd_arbiter.php

xd_arbiter.php

49 ms

xd_arbiter.php

xd_arbiter.php

100 ms

notifications.css

notifications.css

53 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

52 ms

notifications

notifications

51 ms

mixer.gif

mixer.gif

16 ms

jot

jot

78 ms

xd_arbiter.php

xd_arbiter.php

7 ms

like.php

like.php

98 ms

fan.php

fan.php

291 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

37 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

28 ms

410ucuAGgaJ.css

410ucuAGgaJ.css

4 ms

tSbl8xBI27R.css

tSbl8xBI27R.css

8 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

14 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

54 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

53 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

52 ms

36273_177798145581810_4941170_n.jpg

36273_177798145581810_4941170_n.jpg

93 ms

10423859_724125677677658_8165924212364219158_n.jpg

10423859_724125677677658_8165924212364219158_n.jpg

19 ms

10502036_848167228528470_2475124167812168572_n.jpg

10502036_848167228528470_2475124167812168572_n.jpg

24 ms

10354889_690330984376886_6068468764829761732_n.jpg

10354889_690330984376886_6068468764829761732_n.jpg

22 ms

12192000_1640415599530078_6393093477281025088_n.jpg

12192000_1640415599530078_6393093477281025088_n.jpg

22 ms

1424510_628033280572422_1171106550_n.jpg

1424510_628033280572422_1171106550_n.jpg

22 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

17 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

15 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

4 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

8 ms

Accessibility Review

webstory.my accessibility score

92

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

Best Practices

webstory.my best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

webstory.my SEO score

88

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

webstory.my

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