Tools & Wizards About Us
blog.my.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

blog.my.com

My.com — communication and entertainment services: myMail and games.

Page Load Speed

11.9 sec in total

First Response

826 ms

Resources Loaded

9.6 sec

Page Rendered

1.5 sec

blog.my.com screenshot

About Website

Visit blog.my.com now to see the best up-to-date Blog My content for Russia and also check out these interesting facts you probably never knew about blog.my.com

My.com provides a suite of communication and entertainment services: myMail and games. Manage your emails, navigate easier both online and offline, discover captivating new games.

Visit blog.my.com

Key Findings

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

Performance Metrics

blog.my.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value15.5 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value3,400 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.263

47/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

blog.my.com

826 ms

analytics.js

20 ms

wp-emoji-release.min.js

274 ms

css

23 ms

style.css

558 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 47% of them (28 requests) were addressed to the original Blog.my.com, 20% (12 requests) were made to Img.staticmy.com and 19% (11 requests) were made to Games.my.com. The less responsive or slowest element that took the longest time to load (8 sec) relates to the external source Img.staticmy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 355.6 kB (20%)

Content Size

1.7 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blog.my.com main page is 1.7 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. 45% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 98.6 kB

  • Original 145.1 kB
  • After minification 142.9 kB
  • After compression 46.5 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 98.6 kB or 68% of the original size.

Image Optimization

-5%

Potential reduce by 59.4 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. Blog My images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 98.0 kB

  • Original 165.7 kB
  • After minification 164.3 kB
  • After compression 67.8 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 98.0 kB or 59% of the original size.

CSS Optimization

-78%

Potential reduce by 99.6 kB

  • Original 127.9 kB
  • After minification 106.0 kB
  • After compression 28.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. Blog.my.com needs all CSS files to be minified and compressed as it can save up to 99.6 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (30%)

Requests Now

47

After Optimization

33

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blog.my.com

blog.my.com

826 ms

analytics.js

analytics.js

20 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

274 ms

css

css

23 ms

style.css

style.css

558 ms

css

css

37 ms

genericons.css

genericons.css

285 ms

style.css

style.css

200 ms

app.css

app.css

278 ms

jquery.js

jquery.js

749 ms

jquery-migrate.min.js

jquery-migrate.min.js

297 ms

collect

collect

40 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

233 ms

functions.js

functions.js

300 ms

wp-embed.min.js

wp-embed.min.js

250 ms

d16722803.gif

d16722803.gif

673 ms

facebook-64.png

facebook-64.png

328 ms

twitter-64.png

twitter-64.png

329 ms

instagram-64.png

instagram-64.png

111 ms

behance-64.png

behance-64.png

110 ms

dribbble-64.png

dribbble-64.png

110 ms

P20pDYIBONQ.jpg

P20pDYIBONQ.jpg

541 ms

1-825x510.jpg

1-825x510.jpg

369 ms

%D0%B4%D0%BB%D1%8F-%D0%B1%D0%BB%D0%BE%D0%B3%D0%B01-1.png

%D0%B4%D0%BB%D1%8F-%D0%B1%D0%BB%D0%BE%D0%B3%D0%B01-1.png

377 ms

3-1.jpg

3-1.jpg

688 ms

will-you-marry-me-sign-1.jpg

will-you-marry-me-sign-1.jpg

929 ms

7.jpg

7.jpg

613 ms

9-825x510.jpg

9-825x510.jpg

555 ms

10.jpg

10.jpg

754 ms

bk-823x510.jpg

bk-823x510.jpg

718 ms

ID_Art_FB-1.jpg

ID_Art_FB-1.jpg

928 ms

my-com-logo-red.png

my-com-logo-red.png

773 ms

external.min.js

external.min.js

6534 ms

opensans-regular-webfont.woff

opensans-regular-webfont.woff

1003 ms

opensans-light-webfont.woff

opensans-light-webfont.woff

341 ms

opensans-semibold-webfont.woff

opensans-semibold-webfont.woff

5371 ms

opensans-bold-webfont.woff

opensans-bold-webfont.woff

360 ms

opensans-extrabold-webfont.woff

opensans-extrabold-webfont.woff

7993 ms

Genericons.svg

Genericons.svg

771 ms

8AAnjaY2BgYGQAgjO2i86D6AshzNIwGgBAmQUAAAA=

8AAnjaY2BgYGQAgjO2i86D6AshzNIwGgBAmQUAAAA=

3 ms

opensans-italic-webfont.woff

opensans-italic-webfont.woff

521 ms

opensans-lightitalic-webfont.woff

opensans-lightitalic-webfont.woff

540 ms

opensans-semibolditalic-webfont.woff

opensans-semibolditalic-webfont.woff

704 ms

opensans-bolditalic-webfont.woff

opensans-bolditalic-webfont.woff

736 ms

opensans-extrabolditalic-webfont.woff

opensans-extrabolditalic-webfont.woff

887 ms

count.js

count.js

212 ms

count-data.js

count-data.js

65 ms

270f3e0.png

270f3e0.png

266 ms

home.png

home.png

84 ms

1fd50f2.png

1fd50f2.png

345 ms

bd82768.png

bd82768.png

259 ms

b9b64e8.png

b9b64e8.png

351 ms

8569c5a.png

8569c5a.png

522 ms

4536e1a.png

4536e1a.png

524 ms

3d1b362.png

3d1b362.png

431 ms

daba993.png

daba993.png

431 ms

26f1a65.png

26f1a65.png

516 ms

68697d0.png

68697d0.png

522 ms

774780c.png

774780c.png

518 ms

Accessibility Review

blog.my.com accessibility score

72

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

Links do not have a discernible name

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

blog.my.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Page has valid source maps

SEO Factors

blog.my.com SEO score

92

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blog.my.com 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 Blog.my.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

blog.my.com

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