Report Summary

  • 0

    Performance

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

Page Load Speed

9.1 sec in total

First Response

2 sec

Resources Loaded

6.6 sec

Page Rendered

466 ms

xmbroker.direct screenshot

About Website

Visit xmbroker.direct now to see the best up-to-date Xmbroker content for Indonesia and also check out these interesting facts you probably never knew about xmbroker.direct

Visit xmbroker.direct

Key Findings

We analyzed Xmbroker.direct page load time and found that the first response time was 2 sec and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

xmbroker.direct performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value16.0 s

0/100

10%

TBT (Total Blocking Time)

Value2,590 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.058

98/100

15%

TTI (Time to Interactive)

Value23.7 s

1/100

10%

Network Requests Diagram

www.xmindonesiatrade.com

2010 ms

FX72H-U393W-CNX6U-WRWHF-88HB7

19 ms

www.xmindonesiatrade.com

1883 ms

config.json

44 ms

gtm.js

62 ms

Our browser made a total of 150 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Xmbroker.direct, 7% (11 requests) were made to D.adroll.com and 5% (7 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Xmindonesiatrade.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 241.1 kB (19%)

Content Size

1.3 MB

After Optimization

1.1 MB

In fact, the total size of Xmbroker.direct main page is 1.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 670.4 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 40.4 kB

  • Original 61.9 kB
  • After minification 61.8 kB
  • After compression 21.5 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 40.4 kB or 65% of the original size.

Image Optimization

-11%

Potential reduce by 55.6 kB

  • Original 484.7 kB
  • After minification 429.0 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, Xmbroker needs image optimization as it can save up to 55.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-14%

Potential reduce by 91.7 kB

  • Original 670.4 kB
  • After minification 670.3 kB
  • After compression 578.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 91.7 kB or 14% of the original size.

CSS Optimization

-62%

Potential reduce by 53.3 kB

  • Original 86.2 kB
  • After minification 85.8 kB
  • After compression 32.9 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. Xmbroker.direct needs all CSS files to be minified and compressed as it can save up to 53.3 kB or 62% of the original size.

Requests Breakdown

Number of requests can be reduced by 79 (63%)

Requests Now

126

After Optimization

47

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

Accessibility Review

xmbroker.direct accessibility score

81

Accessibility Issues

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

Document doesn't have a <title> element

High

<frame> or <iframe> elements do not have a title

Best Practices

xmbroker.direct 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

xmbroker.direct SEO score

75

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

Document doesn't have a <title> element

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xmbroker.direct 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), while the claimed language is English. Our system also found out that Xmbroker.direct 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

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