Tools & Wizards About Us
makesense.app screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

makesense.app

MakeSense is the community of people, who are ready to share their real-life experience for good causes

Page Load Speed

4.1 sec in total

First Response

219 ms

Resources Loaded

2.9 sec

Page Rendered

1 sec

makesense.app screenshot

About Website

Welcome to makesense.app homepage info - get ready to check Make Sense best content for Belarus right away, or after learning these important things about makesense.app

At MakeSense community: - auction off a useful experience with yourself; - search, bid, win a useful experience with an interesting person; - raised funds are donated to charitable causes

Visit makesense.app

Key Findings

We analyzed Makesense.app page load time and found that the first response time was 219 ms and then it took 3.9 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

makesense.app performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value32.7 s

0/100

25%

SI (Speed Index)

Value13.7 s

2/100

10%

TBT (Total Blocking Time)

Value200 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.39

26/100

15%

TTI (Time to Interactive)

Value32.1 s

0/100

10%

Network Requests Diagram

makesense.app

219 ms

makesense.app

410 ms

tag.js

917 ms

css

36 ms

css

48 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Makesense.app, 74% (56 requests) were made to Makesense-static-media.s3.amazonaws.com and 13% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Makesense-static-media.s3.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (9%)

Content Size

16.8 MB

After Optimization

15.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Makesense.app main page is 16.8 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. 65% of websites need less resources to load. Images take 15.2 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 93.1 kB

  • Original 102.9 kB
  • After minification 84.7 kB
  • After compression 9.8 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. This page needs HTML code to be minified as it can gain 18.3 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 93.1 kB or 90% of the original size.

Image Optimization

-3%

Potential reduce by 392.7 kB

  • Original 15.2 MB
  • After minification 14.8 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. Make Sense images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 657.8 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 423.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 657.8 kB or 61% of the original size.

CSS Optimization

-88%

Potential reduce by 337.1 kB

  • Original 382.6 kB
  • After minification 301.2 kB
  • After compression 45.4 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. Makesense.app needs all CSS files to be minified and compressed as it can save up to 337.1 kB or 88% of the original size.

Requests Breakdown

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

Requests Now

62

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

makesense.app

makesense.app

219 ms

makesense.app

makesense.app

410 ms

tag.js

tag.js

917 ms

css

css

36 ms

css

css

48 ms

bootstrap.min.css

bootstrap.min.css

760 ms

fa-svg-with-js.css

fa-svg-with-js.css

447 ms

pe-icon-7-stroke.css

pe-icon-7-stroke.css

441 ms

magnific-popup.css

magnific-popup.css

440 ms

slick.css

slick.css

442 ms

slick-theme.css

slick-theme.css

467 ms

animate.css

animate.css

664 ms

style.css

style.css

797 ms

responsive.css

responsive.css

771 ms

jquery-3.2.1.min.js

jquery-3.2.1.min.js

887 ms

jquery-migrate.min.js

jquery-migrate.min.js

586 ms

bootstrap.min.js

bootstrap.min.js

885 ms

fontawesome-all.js

fontawesome-all.js

1184 ms

modernizr.custom.js

modernizr.custom.js

910 ms

jquery.easing.js

jquery.easing.js

1008 ms

jquery.stellar.min.js

jquery.stellar.min.js

1009 ms

jquery.scrollto.js

jquery.scrollto.js

1011 ms

jquery.appear.js

jquery.appear.js

1010 ms

slick.min.js

slick.min.js

1018 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

1018 ms

jquery.ajaxchimp.min.js

jquery.ajaxchimp.min.js

1054 ms

contact-form.js

contact-form.js

1053 ms

quick-form.js

quick-form.js

1054 ms

comment-form.js

comment-form.js

1146 ms

jquery.validate.min.js

jquery.validate.min.js

1137 ms

preloader.js

preloader.js

1144 ms

custom.js

custom.js

1155 ms

gsap.min.js

gsap.min.js

28 ms

gsap.min.js

gsap.min.js

14 ms

logo_rounded.png

logo_rounded.png

1068 ms

header-appstore.png

header-appstore.png

1222 ms

header-googleplay.png

header-googleplay.png

1221 ms

380x655.png

380x655.png

1593 ms

400x675-1.png

400x675-1.png

1600 ms

400x800-1.png

400x800-1.png

1828 ms

appstore-grey.png

appstore-grey.png

1222 ms

googleplay-grey.png

googleplay-grey.png

1284 ms

400x675-2.png

400x675-2.png

1627 ms

400x800-2.png

400x800-2.png

1124 ms

400x675-3.png

400x675-3.png

1674 ms

screen-1.png

screen-1.png

1298 ms

screen-2.png

screen-2.png

1401 ms

screen-3.png

screen-3.png

1400 ms

screen-4.png

screen-4.png

1310 ms

screen-5.png

screen-5.png

1255 ms

400x800-3.png

400x800-3.png

1376 ms

review-author-1.jpg

review-author-1.jpg

1204 ms

review-author-2.jpg

review-author-2.jpg

1115 ms

review-author-3.jpg

review-author-3.jpg

1146 ms

review-author-4.jpg

review-author-4.jpg

1130 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

113 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

120 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

112 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

112 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

120 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

123 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

120 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

120 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

119 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

121 ms

Pe-icon-7-stroke.woff

Pe-icon-7-stroke.woff

1179 ms

review-author-5.jpg

review-author-5.jpg

1109 ms

review-author-6.jpg

review-author-6.jpg

1146 ms

hero-5.png

hero-5.png

1167 ms

world-map.png

world-map.png

1257 ms

tra-bg-2.png

tra-bg-2.png

1213 ms

tra-waves.png

tra-waves.png

1228 ms

back-to-top.png

back-to-top.png

964 ms

advert.gif

advert.gif

381 ms

sync_cookie_image_decide

sync_cookie_image_decide

141 ms

1

1

142 ms

Accessibility Review

makesense.app accessibility score

100

Accessibility Issues

Best Practices

makesense.app best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

makesense.app SEO score

91

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

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 Makesense.app 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 Makesense.app 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

makesense.app

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