Tools & Wizards About Us
mweor.com screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

mweor.com

Mweor - Index

Page Load Speed

1.2 sec in total

First Response

270 ms

Resources Loaded

843 ms

Page Rendered

117 ms

mweor.com screenshot

About Website

Visit mweor.com now to see the best up-to-date Mweor content for United States and also check out these interesting facts you probably never knew about mweor.com

A pseudo realistic pet raising simulation with a healthy dash of fantasy, Mweor is a game which allows you to raise, care for, spar with, and breed mweors, cat-like felines which come in various speci...

Visit mweor.com

Key Findings

We analyzed Mweor.com page load time and found that the first response time was 270 ms and then it took 960 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

mweor.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value4.0 s

81/100

10%

TBT (Total Blocking Time)

Value1,220 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

mweor.com

270 ms

mweor.com

119 ms

utilities.js

83 ms

font-awesome.min.css

73 ms

mweor_green.css

72 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 51% of them (21 requests) were addressed to the original Mweor.com, 7% (3 requests) were made to Platform.twitter.com and 7% (3 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (270 ms) belongs to the original domain Mweor.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 46.2 kB (7%)

Content Size

639.1 kB

After Optimization

593.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mweor.com main page is 639.1 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. 50% of websites need less resources to load. Javascripts take 318.7 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 19.5 kB

  • Original 25.9 kB
  • After minification 25.3 kB
  • After compression 6.4 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 19.5 kB or 75% of the original size.

Image Optimization

-8%

Potential reduce by 22.7 kB

  • Original 273.3 kB
  • After minification 250.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. Mweor images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.2 kB

  • Original 318.7 kB
  • After minification 318.7 kB
  • After compression 317.5 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.

CSS Optimization

-13%

Potential reduce by 2.8 kB

  • Original 21.2 kB
  • After minification 21.2 kB
  • After compression 18.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. Mweor.com needs all CSS files to be minified and compressed as it can save up to 2.8 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (57%)

Requests Now

37

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mweor.com

mweor.com

270 ms

mweor.com

mweor.com

119 ms

utilities.js

utilities.js

83 ms

font-awesome.min.css

font-awesome.min.css

73 ms

mweor_green.css

mweor_green.css

72 ms

mweor_all.css

mweor_all.css

74 ms

index_js.js

index_js.js

75 ms

api.js

api.js

33 ms

widgets.js

widgets.js

150 ms

sdk.js

sdk.js

24 ms

recaptcha__de.js

recaptcha__de.js

55 ms

ga.js

ga.js

23 ms

bkg_body_img.png

bkg_body_img.png

55 ms

banner_top.png

banner_top.png

55 ms

blank.gif

blank.gif

53 ms

bkg_content.png

bkg_content.png

52 ms

index_middle.png

index_middle.png

128 ms

index_login.png

index_login.png

55 ms

newaccount.png

newaccount.png

122 ms

q.png

q.png

128 ms

newaccount_loading.png

newaccount_loading.png

127 ms

banner_bottom.png

banner_bottom.png

128 ms

twitter.png

twitter.png

157 ms

fb.png

fb.png

156 ms

ig.png

ig.png

157 ms

sdk.js

sdk.js

33 ms

__utm.gif

__utm.gif

87 ms

female_black_yellow.png

female_black_yellow.png

109 ms

87 ms

fallback

fallback

38 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

54 ms

fallback__ltr.css

fallback__ltr.css

3 ms

css

css

30 ms

logo_48.png

logo_48.png

16 ms

settings

settings

96 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

18 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

22 ms

like.php

like.php

69 ms

GiNc_6TD3uf.js

GiNc_6TD3uf.js

28 ms

FEppCFCt76d.png

FEppCFCt76d.png

23 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

21 ms

Accessibility Review

mweor.com accessibility score

64

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

mweor.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

mweor.com SEO score

92

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

Image elements do not have [alt] attributes

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

mweor.com

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