Report Summary

  • 91

    Performance

    Renders faster than
    91% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

xprt.im

XPRT.IM | search engine, freelance, development projects - XPRT.IM

Page Load Speed

1.1 sec in total

First Response

270 ms

Resources Loaded

580 ms

Page Rendered

229 ms

xprt.im screenshot

About Website

Click here to check amazing XPRT content. Otherwise, check out these important facts you probably never knew about xprt.im

Xprt.im is an intuitive and powerful search engine platform that crawls all the top freelance candidates and remote projects on the interwebs based on natural language search. The platform is particul...

Visit xprt.im

Key Findings

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

Performance Metrics

xprt.im performance score

91

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value2.1 s

96/100

25%

SI (Speed Index)

Value2.2 s

99/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value3.8 s

90/100

10%

Network Requests Diagram

xprt.im

270 ms

styles.css

33 ms

css

29 ms

xprtlogo.png

17 ms

font

74 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 69% of them (9 requests) were addressed to the original Xprt.im, 8% (1 request) were made to Fonts.googleapis.com and 8% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (270 ms) belongs to the original domain Xprt.im.

Page Optimization Overview & Recommendations

Page size can be reduced by 63.7 kB (77%)

Content Size

82.3 kB

After Optimization

18.6 kB

In fact, the total size of Xprt.im main page is 82.3 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. Only 10% of websites need less resources to load. HTML takes 79.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 62.8 kB

  • Original 79.7 kB
  • After minification 78.9 kB
  • After compression 16.9 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 62.8 kB or 79% of the original size.

Image Optimization

-36%

Potential reduce by 917 B

  • Original 2.5 kB
  • After minification 1.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. Obviously, XPRT needs image optimization as it can save up to 917 B or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 56 B

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.

Requests Breakdown

Number of requests can be reduced by 7 (64%)

Requests Now

11

After Optimization

4

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

Accessibility Review

xprt.im accessibility score

63

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

xprt.im best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

xprt.im 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 Xprt.im 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 Xprt.im 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 data is detected on the main page of XPRT. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: