Tools & Wizards About Us
morxe.com screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

morxe.com

NameBright - Coming Soon

Page Load Speed

8.8 sec in total

First Response

4.1 sec

Resources Loaded

4.5 sec

Page Rendered

150 ms

morxe.com screenshot

About Website

Click here to check amazing Morxe content for Italy. Otherwise, check out these important facts you probably never knew about morxe.com

Search on multiple engines.

Visit morxe.com

Key Findings

We analyzed Morxe.com page load time and found that the first response time was 4.1 sec and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

morxe.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.7 s

99/100

25%

SI (Speed Index)

Value1.1 s

100/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.5 s

100/100

10%

Network Requests Diagram

morxe.com

4140 ms

css

24 ms

visio.css

73 ms

bootstrap.min.css

193 ms

style.css

129 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 75% of them (12 requests) were addressed to the original Morxe.com, 13% (2 requests) were made to Google-analytics.com and 6% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Morxe.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 314.8 kB (76%)

Content Size

415.4 kB

After Optimization

100.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 8.1 kB

  • Original 10.8 kB
  • After minification 7.3 kB
  • After compression 2.7 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 3.5 kB, which is 32% 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 8.1 kB or 75% of the original size.

Image Optimization

-8%

Potential reduce by 219 B

  • Original 2.6 kB
  • After minification 2.4 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. Morxe images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 144.8 kB

  • Original 216.2 kB
  • After minification 206.5 kB
  • After compression 71.4 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 144.8 kB or 67% of the original size.

CSS Optimization

-87%

Potential reduce by 161.6 kB

  • Original 185.8 kB
  • After minification 148.6 kB
  • After compression 24.2 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. Morxe.com needs all CSS files to be minified and compressed as it can save up to 161.6 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (69%)

Requests Now

13

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

morxe.com

morxe.com

4140 ms

css

css

24 ms

visio.css

visio.css

73 ms

bootstrap.min.css

bootstrap.min.css

193 ms

style.css

style.css

129 ms

jquery.min.js

jquery.min.js

218 ms

bootstrap.min.js

bootstrap.min.js

143 ms

jquery.parallax.js

jquery.parallax.js

136 ms

social-likes.js

social-likes.js

152 ms

script.js

script.js

187 ms

a

a

11 ms

logo.png

logo.png

67 ms

vegur-light-webfont.woff

vegur-light-webfont.woff

67 ms

analytics.js

analytics.js

16 ms

vegur-regular-webfont.woff

vegur-regular-webfont.woff

59 ms

collect

collect

15 ms

Accessibility Review

morxe.com accessibility score

90

Accessibility Issues

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

Best Practices

morxe.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

morxe.com SEO score

67

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Morxe.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Morxe.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

morxe.com

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