Tools & Wizards About Us
onsay.me screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    72% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

onsay.me

onsay.me

Page Load Speed

4.1 sec in total

First Response

536 ms

Resources Loaded

3.1 sec

Page Rendered

414 ms

onsay.me screenshot

About Website

Welcome to onsay.me homepage info - get ready to check Onsay best content right away, or after learning these important things about onsay.me

This domain may be for sale!

Visit onsay.me

Key Findings

We analyzed Onsay.me page load time and found that the first response time was 536 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

onsay.me performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.392

26/100

15%

TTI (Time to Interactive)

Value3.2 s

94/100

10%

Network Requests Diagram

onsay.me

536 ms

www.onsay.me

614 ms

jquery.min.js

583 ms

jquery.easing.1.3.js

301 ms

jquery.coda-slider-2.0.js

314 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 49% of them (38 requests) were addressed to the original Onsay.me, 28% (22 requests) were made to Static.xx.fbcdn.net and 10% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Onsay.me.

Page Optimization Overview & Recommendations

Page size can be reduced by 165.4 kB (23%)

Content Size

709.8 kB

After Optimization

544.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Onsay.me main page is 709.8 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. 60% of websites need less resources to load. Images take 553.6 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 15.4 kB

  • Original 22.1 kB
  • After minification 19.6 kB
  • After compression 6.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 2.5 kB, which is 11% 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 15.4 kB or 69% of the original size.

Image Optimization

-12%

Potential reduce by 65.4 kB

  • Original 553.6 kB
  • After minification 488.2 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. Obviously, Onsay needs image optimization as it can save up to 65.4 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-62%

Potential reduce by 79.3 kB

  • Original 127.1 kB
  • After minification 110.7 kB
  • After compression 47.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 79.3 kB or 62% of the original size.

CSS Optimization

-77%

Potential reduce by 5.4 kB

  • Original 7.0 kB
  • After minification 5.5 kB
  • After compression 1.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. Onsay.me needs all CSS files to be minified and compressed as it can save up to 5.4 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (33%)

Requests Now

76

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

onsay.me

onsay.me

536 ms

www.onsay.me

www.onsay.me

614 ms

jquery.min.js

jquery.min.js

583 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

301 ms

jquery.coda-slider-2.0.js

jquery.coda-slider-2.0.js

314 ms

onsay.css

onsay.css

350 ms

jquery.page-scroller-308.js

jquery.page-scroller-308.js

361 ms

widget.js

widget.js

59 ms

popupwindow-1.8.1.js

popupwindow-1.8.1.js

542 ms

widgets.js

widgets.js

90 ms

logo_pc_en.png

logo_pc_en.png

609 ms

whats_pc_en.png

whats_pc_en.png

292 ms

onsaysiteWEB_54.png

onsaysiteWEB_54.png

848 ms

onsaysiteWEB_55.png

onsaysiteWEB_55.png

959 ms

onsaysiteWEB_56.png

onsaysiteWEB_56.png

939 ms

download_pc.png

download_pc.png

609 ms

onsaysiteWEB_92.png

onsaysiteWEB_92.png

478 ms

onsaysiteWEB_61.png

onsaysiteWEB_61.png

608 ms

onsaysiteWEB_62.png

onsaysiteWEB_62.png

903 ms

onsaysiteWEB_63.png

onsaysiteWEB_63.png

747 ms

onsaysiteWEB_64.png

onsaysiteWEB_64.png

781 ms

onsaysiteWEB_77.png

onsaysiteWEB_77.png

891 ms

onsaysiteWEB_78.png

onsaysiteWEB_78.png

962 ms

onsaysiteWEB_79.png

onsaysiteWEB_79.png

1015 ms

onsaysiteWEB_80.png

onsaysiteWEB_80.png

1036 ms

social_b.png

social_b.png

1055 ms

onsaysiteWEB_93.png

onsaysiteWEB_93.png

1093 ms

onsaysiteWEB_41.png

onsaysiteWEB_41.png

1137 ms

onsaysiteWEB_42.png

onsaysiteWEB_42.png

1140 ms

onsaysiteWEB_43.png

onsaysiteWEB_43.png

1184 ms

onsaysiteWEB_96.png

onsaysiteWEB_96.png

1178 ms

onsaysiteWEB_94.png

onsaysiteWEB_94.png

1204 ms

onsaysiteWEB_02.png

onsaysiteWEB_02.png

1246 ms

onsaysiteWEB_88.png

onsaysiteWEB_88.png

1314 ms

onsaysiteWEB_72.png

onsaysiteWEB_72.png

1276 ms

onsaysiteWEB_25.png

onsaysiteWEB_25.png

1423 ms

onsaysiteWEB_33.png

onsaysiteWEB_33.png

1477 ms

onsaysiteWEB_40.png

onsaysiteWEB_40.png

1299 ms

onsaysiteWEB_48.png

onsaysiteWEB_48.png

1345 ms

ga.js

ga.js

28 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

132 ms

ajax-loader.gif

ajax-loader.gif

1419 ms

__utm.gif

__utm.gif

19 ms

like.php

like.php

157 ms

likebox.php

likebox.php

273 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

56 ms

TY3MhkXpWJ-.js

TY3MhkXpWJ-.js

34 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

26 ms

McLpmVM3wCm.css

McLpmVM3wCm.css

14 ms

VH4VPudaxfN.css

VH4VPudaxfN.css

9 ms

Czh0gDTFcBt.css

Czh0gDTFcBt.css

18 ms

hhn-1r1gAPt.css

hhn-1r1gAPt.css

19 ms

X97l7PURgJ9.css

X97l7PURgJ9.css

34 ms

1kPfZUdGrka.js

1kPfZUdGrka.js

51 ms

Yuj_Y8xNH2C.js

Yuj_Y8xNH2C.js

70 ms

Mpe38fuBVZ2.js

Mpe38fuBVZ2.js

49 ms

n8qIhCw3vMx.js

n8qIhCw3vMx.js

49 ms

QKy94bWvcbp.js

QKy94bWvcbp.js

86 ms

6q5od22S-uf.js

6q5od22S-uf.js

89 ms

7B-2ZS3Qt8r.js

7B-2ZS3Qt8r.js

92 ms

qcMicXoOToy.js

qcMicXoOToy.js

100 ms

57RpJa05x58.js

57RpJa05x58.js

90 ms

jot

jot

240 ms

165448_349223995148040_2127866710_n.jpg

165448_349223995148040_2127866710_n.jpg

100 ms

safe_image.php

safe_image.php

514 ms

12509137_1690389554541594_2288787239046616905_n.jpg

12509137_1690389554541594_2288787239046616905_n.jpg

108 ms

12115433_1655645148054007_4086683126714451716_n.jpg

12115433_1655645148054007_4086683126714451716_n.jpg

89 ms

12112173_502572126588253_8641517142497762253_n.jpg

12112173_502572126588253_8641517142497762253_n.jpg

83 ms

12742740_1116652758375309_98086084126901055_n.jpg

12742740_1116652758375309_98086084126901055_n.jpg

67 ms

12115710_1675907719356811_5726044295956081459_n.jpg

12115710_1675907719356811_5726044295956081459_n.jpg

74 ms

12645227_990611687689826_4580267645955421966_n.jpg

12645227_990611687689826_4580267645955421966_n.jpg

112 ms

307632_254612041247354_1780826808_n.jpg

307632_254612041247354_1780826808_n.jpg

68 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

27 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

26 ms

QDwYpIaRyfG.png

QDwYpIaRyfG.png

26 ms

K00K-UgnsKu.png

K00K-UgnsKu.png

27 ms

VXcANLwwL5J.js

VXcANLwwL5J.js

3 ms

AmlxWlqMvlv.js

AmlxWlqMvlv.js

6 ms

Accessibility Review

onsay.me accessibility score

94

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.

Best Practices

onsay.me 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

SEO Factors

onsay.me SEO score

100

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Onsay.me can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Onsay.me 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

onsay.me

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