Wease.im - SEO Checker - Website Review

Your Website Score is

Similar Ranking

ONLINE NOTEPAD ---- AT ANOTEPAD.COM

anotepad.com

THIS OFFER IS NOT AVAILABLE IN YOUR COUNTRY

nextyourcontent.com

سامانه بانکداری اینترنتی بانک سپه

ebanksepah.ir

YOU ARE BEING REDIRECTED...

frmoda.com

WHERE PROFESSIONAL MODELS MEET MODEL PHOTOGRAPHERS - MODELMAYHEM - MODELMAYHEM

modelmayhem.com

VERTBAUDET: BABY CLOTHES, CHILDRENSWEAR, MATERNITY & HOME COLLECTION

vertbaudet.com

SEARCH MANAGER

srchmgrk.com

Latest Sites

OSLOWAY | YOUR BEST LOCAL TOURS AND EXPERIENCES IN OSLO

osloway.no

JUST A MOMENT...

hourlyminer.com

ピアノ教室ネット｜先生との出会いはここから。全国のピアノ教室から検索！

pnet.kawai.jp

ADAGIETTOピアノ教室|飯能|ピアノに興味がある皆さんへ|

adagiettopiano.com

ГЛАВНАЯ | UNIEX

uniex.biz

AHMADIMADO - TRUSTED DOGECOIN CLOUD MINING

ahmadimado.net

DOGESILVA LIMITED - HOME

dogesilva.com

Top Technologies

Nginx

Web Servers

PHP

Programming Languages

Google Tag Manager

Tag Managers

Google Font API

Font Scripts

CloudFlare

CDN

jQuery

JavaScript Frameworks

Apache

Web Servers

Font Awesome

Font Scripts

WordPress

CMS

Twitter Bootstrap

Web Frameworks

6 wease.im Last Updated: 9 months

Success 54% of passed verification steps

Warning 23% of total warning

Errors 23% of total errors, require fast action

Mobile

Performance Desktop Score 46%

Best Practices Desktop Score 69%

SEO Desktop Score 91%

Progressive Web App Desktop Score 12%

Performance Mobile Score 6%

Best Practices Mobile Score 69%

SEO Mobile Score 92%

Progressive Web App Mobile Score 15%

Page Authority Authority 30%

Domain Authority Domain Authority 21%

Moz Rank 3.0/10

Bounce Rate Rate 0%

Charset Encoding

Great, language/character encoding is specified: UTF-8

Title Tag 44 Characters

WEASE MESSENGER | SIMPLE AND FAST MESSAGING‎

Meta Description 94 Characters

Over 10 million active users, join the safest messaging Wease app on the market. Download now.

Effective URL 20 Characters

https://www.wease.im

Excerpt Page content

Wease Messenger | Simple and fast messaging‎ ...

Keywords Cloud Density

wease5 designed4 message3 windows3 touch3 ---2 what2 communication2 business2 contact2

Keyword Consistency Keyword density is one of the main terms in SEO

Keyword	Freq	Title	Desc	Domain	H1	H2
wease	5
designed	4
message	3
windows	3
touch	3
---	2
what	2
communication	2
business	2
contact	2

Google Preview Your look like this in google search result

WEASE MESSENGER | SIMPLE AND FAST MESSAGING‎

https://www.wease.im

Over 10 million active users, join the safest messaging Wease app on the market. Download now.

Robots.txt File Detected

http://wease.im/robots.txt

Sitemap.xml File Detected

http://wease.im/sitemap.xml

Page Size Code & Text Ratio

Document Size: ~76.43 KB

Code Size: ~54.2 KB

Text Size: ~22.23 KB Ratio: 29.09%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

PWA - Manifest

Manifest is not valid

Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Speed Index 4.0 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 2.6 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoid enormous network payloads Total size was 3,224 KB

Large network payloads cost users real money and are highly correlated with long load times

robots.txt is not valid 1,049 errors found

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed

Minimizes main-thread work 1.7 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 1.8 s

First Contentful Paint marks the time at which the first text or image is painted

Includes front-end JavaScript libraries with known security vulnerabilities 8 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 48 chains found

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load

Avoids an excessive DOM size 340 elements

A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)

Minify JavaScript Potential savings of 4 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 2.5 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 73 requests • 3,224 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 57 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 110 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 3.6 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Network Round Trip Times 0 ms

Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance

Page load is not fast enough on mobile networks Interactive on simulated mobile network at 15.6 s

A fast page load over a cellular network ensures a good mobile user experience

Estimated Input Latency 10 ms

Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy

Minify CSS Potential savings of 4 KB

Minifying CSS files can reduce network payload sizes

Remove unused CSS Potential savings of 135 KB

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Serve images in next-gen formats Potential savings of 1,082 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Does not use HTTPS 1 insecure request found

All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs

Server response times are low (TTFB) Root document took 380 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 1,770 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Enable text compression Potential savings of 958 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Efficiently encode images Potential savings of 74 KB

Optimized images load faster and consume less cellular data

Minimize third-party usage Third-party code blocked the main thread for 0 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading

Total Blocking Time 50 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

JavaScript execution time 0.8 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Server Backend Latencies 0 ms

Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance

Properly size images Potential savings of 385 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Mobile

Estimated Input Latency 150 ms

First Contentful Paint (3G) 13926 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Minify CSS Potential savings of 4 KB

Minifying CSS files can reduce network payload sizes

Tap targets are sized appropriately 100% appropriately sized tap targets

Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements

Document uses legible font sizes 100% legible text

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px

Remove unused CSS Potential savings of 136 KB

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Serve images in next-gen formats Potential savings of 1,082 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Does not use HTTPS 1 insecure request found

Server response times are low (TTFB) Root document took 200 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 6,090 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Efficiently encode images Potential savings of 74 KB

Optimized images load faster and consume less cellular data

Enable text compression Potential savings of 958 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Minimize third-party usage Third-party code blocked the main thread for 0 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading

Total Blocking Time 690 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 3.5 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Server Backend Latencies 0 ms

Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance

Defer offscreen images Potential savings of 65 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Properly size images Potential savings of 275 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 14.3 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 12.9 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoid enormous network payloads Total size was 3,210 KB

Large network payloads cost users real money and are highly correlated with long load times

robots.txt is not valid 1,049 errors found

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed

Minimize main-thread work 6.6 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 7.0 s

First Contentful Paint marks the time at which the first text or image is painted

Includes front-end JavaScript libraries with known security vulnerabilities 8 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 48 chains found

Avoids an excessive DOM size 340 elements

Minify JavaScript Potential savings of 4 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 10.1 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 73 requests • 3,210 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 57 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 540 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 15.2 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Network Round Trip Times 0 ms

Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance

Page load is not fast enough on mobile networks Interactive at 15.2 s

A fast page load over a cellular network ensures a good mobile user experience

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server

HTTP/1.1 302 Found
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 26 Nov 2019 12:12:23 GMT
Content-Type: text/html; charset=UTF-8
Location: https://www.wease.im
X-Backend-Server: f2

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	wease.im	212.129.33.171	IN	6533
NS	wease.im	c.dns.gandi.net	IN	6580
NS	wease.im	a.dns.gandi.net	IN	6580
NS	wease.im	b.dns.gandi.net	IN	6580
MX	wease.im	ASPMX3.GOOGLEMAIL.COM	IN	6580
MX	wease.im	ASPMX5.GOOGLEMAIL.COM	IN	6580
MX	wease.im	ALT2.ASPMX.L.GOOGLE.COM	IN	6580
MX	wease.im	ASPMX4.GOOGLEMAIL.COM	IN	6580
MX	wease.im	ASPMX.L.GOOGLE.COM	IN	6580
MX	wease.im	ALT1.ASPMX.L.GOOGLE.COM	IN	6580
MX	wease.im	ASPMX2.GOOGLEMAIL.COM	IN	6580
TXT	wease.im	google-site-verification=59uRcoB0HadreWpsc061hil3N0dcm2Bmvhc97wmUW-Q	IN	2979

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

6 wease.im Last Updated: 9 months

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

Font Awesome

Google Font API

Ionicons

Nginx

PHP

Ubuntu

WordPress

Yoast SEO

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments