Tools & Wizards About Us
dot.jo screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

dot.jo

dot.jo - dot.jo

Page Load Speed

13.2 sec in total

First Response

210 ms

Resources Loaded

9.5 sec

Page Rendered

3.5 sec

dot.jo screenshot

About Website

Click here to check amazing Dot content for Jordan. Otherwise, check out these important facts you probably never knew about dot.jo

The official Website for Dot Jo Comany

Visit dot.jo

Key Findings

We analyzed Dot.jo page load time and found that the first response time was 210 ms and then it took 13 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

dot.jo performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

3/100

25%

SI (Speed Index)

Value5.4 s

55/100

10%

TBT (Total Blocking Time)

Value1,370 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.692

7/100

15%

TTI (Time to Interactive)

Value17.3 s

4/100

10%

Network Requests Diagram

dot.jo

210 ms

dot.jo

443 ms

d9c094ab2579b9604074387c49f33d6d.css

204 ms

all.css

56 ms

8212a3d4168c178903706ac542a1ea37.css

288 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 80% of them (78 requests) were addressed to the original Dot.jo, 8% (8 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Pro.fontawesome.com. The less responsive or slowest element that took the longest time to load (8.8 sec) belongs to the original domain Dot.jo.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (9%)

Content Size

19.8 MB

After Optimization

18.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dot.jo main page is 19.8 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. 75% 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. Images take 19.6 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 37.0 kB

  • Original 45.6 kB
  • After minification 44.7 kB
  • After compression 8.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 37.0 kB or 81% of the original size.

Image Optimization

-9%

Potential reduce by 1.7 MB

  • Original 19.6 MB
  • After minification 17.9 MB

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. Dot images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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

-16%

Potential reduce by 22.1 kB

  • Original 134.0 kB
  • After minification 134.0 kB
  • After compression 112.0 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. Dot.jo needs all CSS files to be minified and compressed as it can save up to 22.1 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (16%)

Requests Now

74

After Optimization

62

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dot. 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 from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

dot.jo

dot.jo

210 ms

dot.jo

dot.jo

443 ms

d9c094ab2579b9604074387c49f33d6d.css

d9c094ab2579b9604074387c49f33d6d.css

204 ms

all.css

all.css

56 ms

8212a3d4168c178903706ac542a1ea37.css

8212a3d4168c178903706ac542a1ea37.css

288 ms

style.css

style.css

385 ms

450e80e02a6ed0e7f43b04b21ca5e07c.css

450e80e02a6ed0e7f43b04b21ca5e07c.css

292 ms

logo-85x85.png

logo-85x85.png

381 ms

widget.js

widget.js

63 ms

loadbuild.js

loadbuild.js

70 ms

js

js

66 ms

d3166f6b1e6eec739049253223b1e96f.js

d3166f6b1e6eec739049253223b1e96f.js

496 ms

custom.js

custom.js

298 ms

1e641f3d557f92efcee620d7150dfbd7.js

1e641f3d557f92efcee620d7150dfbd7.js

592 ms

rocket-gif-480x355.gif

rocket-gif-480x355.gif

494 ms

rpcket-blank.png

rpcket-blank.png

394 ms

php-65x65.png

php-65x65.png

493 ms

html5-3-65x65.png

html5-3-65x65.png

494 ms

js-65x65.png

js-65x65.png

495 ms

bootstrap-65x65.png

bootstrap-65x65.png

570 ms

e9pny4iwyaeuvpc-1-65x65.png

e9pny4iwyaeuvpc-1-65x65.png

589 ms

elbluergb1145x45-65x65.png

elbluergb1145x45-65x65.png

588 ms

sketch-65x65.png

sketch-65x65.png

620 ms

figma-65x65.png

figma-65x65.png

621 ms

invision-65x65.png

invision-65x65.png

690 ms

adobe-xd-65x65.png

adobe-xd-65x65.png

692 ms

kotlinicon-65x65.png

kotlinicon-65x65.png

691 ms

java-logo-700x394-65x65.png

java-logo-700x394-65x65.png

692 ms

handshake-2-40x40.png

handshake-2-40x40.png

764 ms

network-40x40.png

network-40x40.png

764 ms

target-1-40x40.png

target-1-40x40.png

766 ms

jfa.png

jfa.png

1908 ms

eyes-up.png

eyes-up.png

775 ms

eye-full.png

eye-full.png

775 ms

al-salam.png

al-salam.png

1342 ms

nathefa.png

nathefa.png

1511 ms

el-seif.png

el-seif.png

1613 ms

client.gif

client.gif

8811 ms

king-abdullah-2.png

king-abdullah-2.png

875 ms

king-abdullah-2-280x225.png

king-abdullah-2-280x225.png

1052 ms

khcf.png

khcf.png

1148 ms

khcf-280x225.png

khcf-280x225.png

1338 ms

psut.png

psut.png

1217 ms

psut-280x225.png

psut-280x225.png

1158 ms

cbos.png

cbos.png

1250 ms

cbos-280x225.png

cbos-280x225.png

1240 ms

hbtf.png

hbtf.png

1235 ms

css2

css2

35 ms

hbtf-280x225.png

hbtf-280x225.png

1247 ms

jkb.png

jkb.png

1238 ms

jkb-280x225.png

jkb-280x225.png

1211 ms

tamweelcom.png

tamweelcom.png

1218 ms

tamweelcom-280x225.png

tamweelcom-280x225.png

1233 ms

al-ameed.png

al-ameed.png

1232 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hNI-W1Q.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hNI-W1Q.ttf

198 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hOA-W1Q.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hOA-W1Q.ttf

258 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hL4-W1Q.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hL4-W1Q.ttf

370 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hGA-W1Q.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hGA-W1Q.ttf

343 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hD45W1Q.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hD45W1Q.ttf

343 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hAc5W1Q.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hAc5W1Q.ttf

342 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hGA5W1Q.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hGA5W1Q.ttf

362 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hEk5W1Q.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hEk5W1Q.ttf

333 ms

fa-regular-400.woff

fa-regular-400.woff

67 ms

fa-regular-400.woff

fa-regular-400.woff

1305 ms

fa-light-300.woff

fa-light-300.woff

72 ms

fa-solid-900.woff

fa-solid-900.woff

92 ms

js

js

65 ms

analytics.js

analytics.js

59 ms

fa-regular-400.woff

fa-regular-400.woff

1305 ms

fa-light-300.woff

fa-light-300.woff

1238 ms

fa-light-300.woff

fa-light-300.woff

1387 ms

fa-solid-900.woff

fa-solid-900.woff

1278 ms

fa-solid-900.woff

fa-solid-900.woff

1423 ms

al-ameed-280x225.png

al-ameed-280x225.png

1348 ms

collect

collect

131 ms

jordan-football-association.png

jordan-football-association.png

1301 ms

jordan-football-association-280x225.png

jordan-football-association-280x225.png

1311 ms

mfu.png

mfu.png

1371 ms

mfu-280x225.png

mfu-280x225.png

1378 ms

mms.png

mms.png

1321 ms

mms-280x225.png

mms-280x225.png

1331 ms

tot-triangle.png

tot-triangle.png

1366 ms

tot-triangle-280x225.png

tot-triangle-280x225.png

1383 ms

ftr-app-320x165.png

ftr-app-320x165.png

1390 ms

logo-90x90.png

logo-90x90.png

1303 ms

ftr-1.png

ftr-1.png

1138 ms

ftr-3.png

ftr-3.png

1082 ms

ftr-5.png

ftr-5.png

913 ms

facebook-1.png

facebook-1.png

916 ms

twitter-1.png

twitter-1.png

838 ms

linked-1.png

linked-1.png

849 ms

Background.webp

Background.webp

813 ms

Footer.webp

Footer.webp

816 ms

fa-regular-400.ttf

fa-regular-400.ttf

475 ms

fa-light-300.ttf

fa-light-300.ttf

453 ms

fa-solid-900.ttf

fa-solid-900.ttf

330 ms

fa-light-300.svg

fa-light-300.svg

165 ms

Accessibility Review

dot.jo accessibility score

78

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

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

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

dot.jo best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

dot.jo SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    AR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dot.jo can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Arabic language. Our system also found out that Dot.jo 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

dot.jo

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