Tools & Wizards About Us
xtok.com screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

xtok.com

xTok - Tec. Inf., Lda

Page Load Speed

4.3 sec in total

First Response

328 ms

Resources Loaded

3.7 sec

Page Rendered

236 ms

xtok.com screenshot

About Website

Click here to check amazing XTok content. Otherwise, check out these important facts you probably never knew about xtok.com

Um tok no X - Criamos e desenvolvemos software multi-plataforma.

Visit xtok.com

Key Findings

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

Performance Metrics

xtok.com performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

21/100

25%

SI (Speed Index)

Value6.9 s

33/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.8 s

66/100

10%

Network Requests Diagram

xtok.com

328 ms

xGest

405 ms

xGest

764 ms

estilos.css

103 ms

estilos.css

197 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 29% of them (12 requests) were addressed to the original Xtok.com, 68% (28 requests) were made to Blogtok.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (764 ms) belongs to the original domain Xtok.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 108.0 kB (38%)

Content Size

287.4 kB

After Optimization

179.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Xtok.com main page is 287.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. 20% of websites need less resources to load. Images take 159.9 kB which makes up the majority of the site volume.

HTML Optimization

-55%

Potential reduce by 38.6 kB

  • Original 70.3 kB
  • After minification 68.6 kB
  • After compression 31.8 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 38.6 kB or 55% of the original size.

Image Optimization

-24%

Potential reduce by 37.7 kB

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

JavaScript Optimization

-53%

Potential reduce by 26.2 kB

  • Original 49.8 kB
  • After minification 32.6 kB
  • After compression 23.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 26.2 kB or 53% of the original size.

CSS Optimization

-75%

Potential reduce by 5.5 kB

  • Original 7.4 kB
  • After minification 5.8 kB
  • After compression 1.8 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. Xtok.com needs all CSS files to be minified and compressed as it can save up to 5.5 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (13%)

Requests Now

24

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

xtok.com

xtok.com

328 ms

xGest

xGest

405 ms

xGest

xGest

764 ms

estilos.css

estilos.css

103 ms

estilos.css

estilos.css

197 ms

jquery.min.js

jquery.min.js

9 ms

jquery.li-scroller.1.0.js

jquery.li-scroller.1.0.js

406 ms

chrome.js

chrome.js

408 ms

chromestyle.css

chromestyle.css

406 ms

slideshow.js

slideshow.js

408 ms

xmak.jpg

xmak.jpg

305 ms

logo_webmail.png

logo_webmail.png

306 ms

it.jpg

it.jpg

402 ms

avatar.jpg

avatar.jpg

403 ms

43efa3fb3e4b4c0_mini.jpg

43efa3fb3e4b4c0_mini.jpg

434 ms

fundo.jpg

fundo.jpg

102 ms

fb.png

fb.png

239 ms

tw.png

tw.png

204 ms

email.png

email.png

305 ms

jquery.li-scroller.1.0.js

jquery.li-scroller.1.0.js

442 ms

chromestyle.css

chromestyle.css

451 ms

chrome.js

chrome.js

458 ms

slideshow.js

slideshow.js

573 ms

xmak.jpg

xmak.jpg

571 ms

logo_webmail.png

logo_webmail.png

582 ms

it.jpg

it.jpg

442 ms

avatar.jpg

avatar.jpg

452 ms

xsite_logo.jpg

xsite_logo.jpg

442 ms

avatar.jpg

avatar.jpg

518 ms

43efa3fb3e4b4c0_mini.jpg

43efa3fb3e4b4c0_mini.jpg

524 ms

chromebg.gif

chromebg.gif

104 ms

blog.jpg

blog.jpg

103 ms

down.gif

down.gif

103 ms

mp.jpg

mp.jpg

205 ms

mp_topo.jpg

mp_topo.jpg

104 ms

chromebg.gif

chromebg.gif

101 ms

down.gif

down.gif

104 ms

661eaff4067e45a_mini.jpg

661eaff4067e45a_mini.jpg

103 ms

ca739a724efe875_mini.jpg

ca739a724efe875_mini.jpg

102 ms

ca739a724efe875_mini.jpg

ca739a724efe875_mini.jpg

103 ms

661eaff4067e45a_mini.jpg

661eaff4067e45a_mini.jpg

103 ms

Accessibility Review

xtok.com accessibility score

65

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

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

Links do not have a discernible name

Best Practices

xtok.com best practices score

67

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

xtok.com SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xtok.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 Xtok.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

xtok.com

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