Tools & Wizards About Us
masoko.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

masoko.com

Shop Online for Mobile Devices & Accessories | Masoko

Page Load Speed

10.4 sec in total

First Response

237 ms

Resources Loaded

9.8 sec

Page Rendered

361 ms

masoko.com screenshot

About Website

Click here to check amazing Masoko content for Kenya. Otherwise, check out these important facts you probably never knew about masoko.com

Browse & shop from a wide variety of phones and accessories. Safe and secure payments via M-Pesa, credit & debit cards. Sign up today.

Visit masoko.com

Key Findings

We analyzed Masoko.com page load time and found that the first response time was 237 ms and then it took 10.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

masoko.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value14.2 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value4,690 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.038

100/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

masoko.com

237 ms

masoko.com

4756 ms

core-At-like-well-Comes-trantage-in-thinder-Macb

547 ms

slick.min.css

38 ms

slick-theme.min.css

51 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 65% of them (33 requests) were addressed to the original Masoko.com, 10% (5 requests) were made to Googletagmanager.com and 6% (3 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain Masoko.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 130.3 kB (16%)

Content Size

827.5 kB

After Optimization

697.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Masoko.com main page is 827.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 575.9 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 128.0 kB

  • Original 142.9 kB
  • After minification 142.8 kB
  • After compression 14.9 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 128.0 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 575.9 kB
  • After minification 575.9 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. Masoko images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 2.4 kB

  • Original 108.7 kB
  • After minification 108.7 kB
  • After compression 106.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 29 (66%)

Requests Now

44

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

masoko.com

masoko.com

237 ms

masoko.com

masoko.com

4756 ms

core-At-like-well-Comes-trantage-in-thinder-Macb

core-At-like-well-Comes-trantage-in-thinder-Macb

547 ms

slick.min.css

slick.min.css

38 ms

slick-theme.min.css

slick-theme.min.css

51 ms

f6e031e1e20715eb.css

f6e031e1e20715eb.css

371 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

517 ms

6066.c5e34777c38094d7.js

6066.c5e34777c38094d7.js

543 ms

1996.bb3ad81298bb7ebd.js

1996.bb3ad81298bb7ebd.js

381 ms

1491.19a07658b43e0a08.js

1491.19a07658b43e0a08.js

331 ms

webpack-6a856ad7cad19ba9.js

webpack-6a856ad7cad19ba9.js

616 ms

framework-ca706bf673a13738.js

framework-ca706bf673a13738.js

1968 ms

main-790bfd9fc392721e.js

main-790bfd9fc392721e.js

1974 ms

_app-6bb104e1019d6a4a.js

_app-6bb104e1019d6a4a.js

1979 ms

29107295-79b81857c2f2608e.js

29107295-79b81857c2f2608e.js

1966 ms

fec483df-f269a36b5c217e8b.js

fec483df-f269a36b5c217e8b.js

1976 ms

5581-3002f9e03ad579de.js

5581-3002f9e03ad579de.js

2000 ms

5133-a004a83b982df5ac.js

5133-a004a83b982df5ac.js

1997 ms

3203-1cfe5cbc58d9f99b.js

3203-1cfe5cbc58d9f99b.js

1974 ms

index-eb2ae03ab0ea9c33.js

index-eb2ae03ab0ea9c33.js

1976 ms

_buildManifest.js

_buildManifest.js

2560 ms

_ssgManifest.js

_ssgManifest.js

2002 ms

_Incapsula_Resource

_Incapsula_Resource

1914 ms

css2

css2

30 ms

masoko-white.svg

masoko-white.svg

1539 ms

image

image

1541 ms

image

image

4388 ms

image

image

1542 ms

image

image

1542 ms

image

image

1541 ms

image

image

1543 ms

image

image

1545 ms

Futura-Book-BT.8baaa424.ttf

Futura-Book-BT.8baaa424.ttf

1467 ms

FuturaStdMediumOblique.22b15721.woff

FuturaStdMediumOblique.22b15721.woff

1469 ms

slick.woff

slick.woff

73 ms

_Incapsula_Resource

_Incapsula_Resource

132 ms

core-At-like-well-Comes-trantage-in-thinder-Macb

core-At-like-well-Comes-trantage-in-thinder-Macb

627 ms

gtm.js

gtm.js

83 ms

js

js

66 ms

js

js

209 ms

destination

destination

207 ms

fbevents.js

fbevents.js

206 ms

js

js

201 ms

207 ms

206 ms

158 ms

2411731032283739

2411731032283739

75 ms

57 ms

56 ms

22 ms

21 ms

Accessibility Review

masoko.com accessibility score

76

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

masoko.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

masoko.com SEO score

89

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 doesn't use 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 Masoko.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 Masoko.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

masoko.com

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