Tools & Wizards About Us
blog.memsource.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

blog.memsource.com

Global Business and Localization Best Practices | Phrase Blog

Page Load Speed

7.3 sec in total

First Response

2.3 sec

Resources Loaded

4.2 sec

Page Rendered

707 ms

blog.memsource.com screenshot

About Website

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

Keep up with best practices for global business, localization management, internationalization, translation, and updates from Phrase.

Visit blog.memsource.com

Key Findings

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

Performance Metrics

blog.memsource.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

59/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value2,100 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

blog.memsource.com

2334 ms

language-selector.css

213 ms

bwp-recent-comments.css

234 ms

bbpress.css

226 ms

thrive_default.css

228 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 74% of them (51 requests) were addressed to the original Blog.memsource.com, 10% (7 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to S3.amazonaws.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Blog.memsource.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 980.8 kB (48%)

Content Size

2.0 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blog.memsource.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. 60% of websites need less resources to load. Images take 876.6 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 66.1 kB

  • Original 78.6 kB
  • After minification 72.2 kB
  • After compression 12.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 66.1 kB or 84% of the original size.

Image Optimization

-6%

Potential reduce by 52.0 kB

  • Original 876.6 kB
  • After minification 824.6 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. Blog Memsource images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 436.5 kB

  • Original 598.9 kB
  • After minification 480.5 kB
  • After compression 162.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 436.5 kB or 73% of the original size.

CSS Optimization

-88%

Potential reduce by 426.2 kB

  • Original 486.8 kB
  • After minification 407.3 kB
  • After compression 60.6 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.memsource.com needs all CSS files to be minified and compressed as it can save up to 426.2 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (71%)

Requests Now

59

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blog.memsource.com

blog.memsource.com

2334 ms

language-selector.css

language-selector.css

213 ms

bwp-recent-comments.css

bwp-recent-comments.css

234 ms

bbpress.css

bbpress.css

226 ms

thrive_default.css

thrive_default.css

228 ms

thrive_colors.css

thrive_colors.css

227 ms

thrive_flat.css

thrive_flat.css

324 ms

foundation.css

foundation.css

319 ms

font-awesome.min.css

font-awesome.min.css

336 ms

css

css

25 ms

plugins.css

plugins.css

337 ms

style.css

style.css

431 ms

responsive.css

responsive.css

341 ms

style.css

style.css

424 ms

style.css

style.css

429 ms

style.css

style.css

442 ms

style.css

style.css

442 ms

amrusersfront.css

amrusersfront.css

443 ms

jquery.js

jquery.js

638 ms

jquery-migrate.min.js

jquery-migrate.min.js

536 ms

compat.min.js

compat.min.js

536 ms

modernizr.js

modernizr.js

540 ms

current.js

current.js

44 ms

thrive_content_builder_frontend.min.js

thrive_content_builder_frontend.min.js

446 ms

jquery.cookie.min.js

jquery.cookie.min.js

340 ms

plugins.js

plugins.js

595 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

536 ms

packery.pkgd.min.js

packery.pkgd.min.js

535 ms

gridmode.js

gridmode.js

537 ms

olea.js

olea.js

537 ms

jquery.cycle2.min.js

jquery.cycle2.min.js

550 ms

jquery.cycle2.carousel.min.js

jquery.cycle2.carousel.min.js

593 ms

jquery.cycle2.swipe.min.js

jquery.cycle2.swipe.min.js

595 ms

jquery.cycle2.tile.min.js

jquery.cycle2.tile.min.js

595 ms

jquery.cycle2.video.min.js

jquery.cycle2.video.min.js

595 ms

script.js

script.js

652 ms

script.js

script.js

673 ms

client.js

client.js

676 ms

sitepress.js

sitepress.js

673 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

660 ms

2ce7b30b-2e7d-46a6-aa48-6ebd73836786.png

2ce7b30b-2e7d-46a6-aa48-6ebd73836786.png

266 ms

site-memsource.png

site-memsource.png

291 ms

blog-memsource.png

blog-memsource.png

272 ms

pattern-7r8b.png

pattern-7r8b.png

287 ms

IlyaMishchenko_portrait-300x260.png

IlyaMishchenko_portrait-300x260.png

394 ms

LocWorld-Presentation-Memsource-Gengo.png

LocWorld-Presentation-Memsource-Gengo.png

608 ms

patricia-300x200.jpg

patricia-300x200.jpg

403 ms

2015-11-02-_DSC0700-Edit-Edit-281x300.jpg

2015-11-02-_DSC0700-Edit-Edit-281x300.jpg

481 ms

cloud-logo-221x100-3.png

cloud-logo-221x100-3.png

393 ms

pic-300x200.jpg

pic-300x200.jpg

413 ms

14ab5bc.jpg

14ab5bc.jpg

501 ms

Zero-Downtime-Deployment-1.png

Zero-Downtime-Deployment-1.png

1345 ms

Wojciech_Mocek_photo.jpg

Wojciech_Mocek_photo.jpg

512 ms

eCpfeMZI7q4jLksXVRWPQy3USBnSvpkopQaUR-2r7iU.ttf

eCpfeMZI7q4jLksXVRWPQy3USBnSvpkopQaUR-2r7iU.ttf

11 ms

lJAvZoKA5NttpPc9yc6lPfEr6Hm6RMS0v1dtXsGir4g.ttf

lJAvZoKA5NttpPc9yc6lPfEr6Hm6RMS0v1dtXsGir4g.ttf

53 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

684 ms

Y_TKV6o8WovbUd3m_X9aAA.ttf

Y_TKV6o8WovbUd3m_X9aAA.ttf

52 ms

HqHm7BVC_nzzTui2lzQTDaCWcynf_cDxXwCLxiixG1c.ttf

HqHm7BVC_nzzTui2lzQTDaCWcynf_cDxXwCLxiixG1c.ttf

51 ms

bH7276GfdCjMjApa_dkG6aCWcynf_cDxXwCLxiixG1c.ttf

bH7276GfdCjMjApa_dkG6aCWcynf_cDxXwCLxiixG1c.ttf

51 ms

HQXBIwLHsOJCNEQeX9kNz4nF5uFdDttMLvmWuJdhhgs.ttf

HQXBIwLHsOJCNEQeX9kNz4nF5uFdDttMLvmWuJdhhgs.ttf

54 ms

Wreg0Be4tcFGM2t6VWytvH06qf9KHRHwsVx7iw5MXmY.ttf

Wreg0Be4tcFGM2t6VWytvH06qf9KHRHwsVx7iw5MXmY.ttf

53 ms

widget.min.js

widget.min.js

95 ms

analytics.js

analytics.js

50 ms

1871513.js

1871513.js

61 ms

collect

collect

24 ms

widget.min.css

widget.min.css

9 ms

collect

collect

86 ms

loader-v2.js

loader-v2.js

34 ms

__ptq.gif

__ptq.gif

9 ms

Accessibility Review

blog.memsource.com accessibility score

90

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Best Practices

blog.memsource.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

blog.memsource.com SEO score

82

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

Links do not have descriptive text

High

Document doesn't have a valid hreflang

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

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