Tools & Wizards About Us
jaftim.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 48

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

jaftim.com

Quality Used Cars For Sale from UAE Dealer and Exporter - Jaftim Cars

Page Load Speed

17.6 sec in total

First Response

44 ms

Resources Loaded

15.9 sec

Page Rendered

1.6 sec

jaftim.com screenshot

About Website

Click here to check amazing Jaftim content for Pakistan. Otherwise, check out these important facts you probably never knew about jaftim.com

Affordable, High quality used cars from UAE. Hundreds of cars stocked. Exporting worldwide from UAE. Find your perfect car now!

Visit jaftim.com

Key Findings

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

Performance Metrics

jaftim.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value25.8 s

0/100

10%

TBT (Total Blocking Time)

Value1,730 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value14.1 s

9/100

10%

Network Requests Diagram

jaftim.com

44 ms

jaftim.com

143 ms

www.jaftim.com

9952 ms

js

91 ms

css

65 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 19% of them (15 requests) were addressed to the original Jaftim.com, 56% (44 requests) were made to Erp.jaftim.com and 10% (8 requests) were made to Embed.tawk.to. The less responsive or slowest element that took the longest time to load (10 sec) belongs to the original domain Jaftim.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 577.2 kB (12%)

Content Size

4.8 MB

After Optimization

4.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jaftim.com main page is 4.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. 55% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-94%

Potential reduce by 330.4 kB

  • Original 350.0 kB
  • After minification 190.0 kB
  • After compression 19.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 160.0 kB, which is 46% 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 330.4 kB or 94% of the original size.

Image Optimization

-6%

Potential reduce by 219.3 kB

  • Original 3.8 MB
  • After minification 3.6 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. Jaftim images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 26.1 kB

  • Original 440.1 kB
  • After minification 440.1 kB
  • After compression 414.1 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

-1%

Potential reduce by 1.5 kB

  • Original 177.1 kB
  • After minification 177.1 kB
  • After compression 175.6 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. Jaftim.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 25 (34%)

Requests Now

73

After Optimization

48

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jaftim.com

jaftim.com

44 ms

jaftim.com

jaftim.com

143 ms

www.jaftim.com

www.jaftim.com

9952 ms

js

js

91 ms

css

css

65 ms

jquery-1.8.2.min.js

jquery-1.8.2.min.js

51 ms

jquery.cycle.lite.min.js

jquery.cycle.lite.min.js

187 ms

jquery-ui.css

jquery-ui.css

53 ms

jquery-ui.min.js

jquery-ui.min.js

57 ms

common.js

common.js

241 ms

uik.bundle.min.css

uik.bundle.min.css

393 ms

uik.bundle.min.js

uik.bundle.min.js

235 ms

style.css

style.css

248 ms

select2.min.css

select2.min.css

214 ms

select2.min.js

select2.min.js

220 ms

api.js

api.js

71 ms

datepicker.min.js

datepicker.min.js

154 ms

jquery.modal.min.js

jquery.modal.min.js

154 ms

common.js

common.js

468 ms

custom.js

custom.js

275 ms

plugin.js

plugin.js

303 ms

f_thumb.jpeg

f_thumb.jpeg

512 ms

logo-dark.png

logo-dark.png

512 ms

f_thumb.jpg

f_thumb.jpg

512 ms

f_thumb.jpg

f_thumb.jpg

743 ms

f_thumb.jpeg

f_thumb.jpeg

745 ms

f_thumb.jpeg

f_thumb.jpeg

740 ms

f_thumb.jpeg

f_thumb.jpeg

742 ms

f_thumb.jpeg

f_thumb.jpeg

621 ms

f_thumb.jpg

f_thumb.jpg

738 ms

f_thumb.jpeg

f_thumb.jpeg

743 ms

f_thumb.jpg

f_thumb.jpg

740 ms

f_thumb.jpg

f_thumb.jpg

825 ms

f_thumb.jpg

f_thumb.jpg

1619 ms

f_thumb.jpg

f_thumb.jpg

2622 ms

f_thumb.jpg

f_thumb.jpg

809 ms

f_thumb.jpg

f_thumb.jpg

2625 ms

f_thumb.jpg

f_thumb.jpg

3622 ms

f_thumb.jpg

f_thumb.jpg

3627 ms

f_thumb.jpg

f_thumb.jpg

912 ms

f_thumb.jpeg

f_thumb.jpeg

981 ms

f_thumb.jpeg

f_thumb.jpeg

1052 ms

f_thumb.jpg

f_thumb.jpg

1128 ms

f_thumb.jpg

f_thumb.jpg

1230 ms

f_thumb.jpeg

f_thumb.jpeg

1282 ms

f_thumb.jpg

f_thumb.jpg

1332 ms

f_thumb.jpg

f_thumb.jpg

1432 ms

f_thumb.jpg

f_thumb.jpg

3627 ms

f_thumb.jpg

f_thumb.jpg

1697 ms

f_thumb.jpeg

f_thumb.jpeg

4626 ms

f_thumb.jpg

f_thumb.jpg

4633 ms

f_thumb.jpg

f_thumb.jpg

4627 ms

f_thumb.jpeg

f_thumb.jpeg

3694 ms

f_thumb.jpg

f_thumb.jpg

3698 ms

f_thumb.jpeg

f_thumb.jpeg

4631 ms

f_thumb.jpeg

f_thumb.jpeg

4638 ms

f_thumb.jpeg

f_thumb.jpeg

3766 ms

f_thumb.jpg

f_thumb.jpg

3835 ms

recaptcha__en.js

recaptcha__en.js

605 ms

select-1.png

select-1.png

463 ms

fontello.woff

fontello.woff

1120 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

467 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

550 ms

1g6q33mpf

1g6q33mpf

308 ms

blog_2022-09-05_22.png

blog_2022-09-05_22.png

4391 ms

blog_2022-08-31_21.png

blog_2022-08-31_21.png

4429 ms

blog_2022-08-17_20.jpg

blog_2022-08-17_20.jpg

4447 ms

blog_2022-08-11_19.jpg

blog_2022-08-11_19.jpg

4267 ms

review_2022-04-25_44.png

review_2022-04-25_44.png

4288 ms

review_2022-04-13_42.jpeg

review_2022-04-13_42.jpeg

4230 ms

review_2022-04-14_41.jpeg

review_2022-04-14_41.jpeg

4402 ms

review_2022-04-05_37.jpeg

review_2022-04-05_37.jpeg

4395 ms

twk-event-polyfill.js

twk-event-polyfill.js

201 ms

twk-main.js

twk-main.js

38 ms

twk-vendor.js

twk-vendor.js

15 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

132 ms

twk-chunk-common.js

twk-chunk-common.js

139 ms

twk-runtime.js

twk-runtime.js

57 ms

twk-app.js

twk-app.js

25 ms

Accessibility Review

jaftim.com accessibility score

48

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

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

[id] attributes on active, focusable elements are not unique

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

jaftim.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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

jaftim.com 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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jaftim.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Jaftim.com main page’s claimed encoding is . 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

jaftim.com

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