Tools & Wizards About Us

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

tigule.com

Where Buyers and Sellers Meet In Zambia - Tigule Zambia

Page Load Speed

4.9 sec in total

First Response

263 ms

Resources Loaded

4.1 sec

Page Rendered

502 ms

About Website

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

Buy and Sell in Zambia. 1000s of Products and Services, New and Used listed for Sale, Rent or Hire Purchase. tigule.com is where buyers and sellers meet.

Visit tigule.com

Key Findings

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

Performance Metrics

tigule.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value750 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.974

2/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

tigule.com

263 ms

tigule.com

517 ms

css

38 ms

wcfm-style-core.css

234 ms

wcfmvm-style-custom-subscribe-button-1562849462.css

236 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 85% of them (82 requests) were addressed to the original Tigule.com, 10% (10 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Tigule.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (45%)

Content Size

2.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tigule.com main page is 2.7 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-95%

Potential reduce by 1.1 MB

  • Original 1.1 MB
  • After minification 1.0 MB
  • After compression 52.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. This page needs HTML code to be minified as it can gain 119.6 kB, which is 11% 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 1.1 MB or 95% of the original size.

Image Optimization

-10%

Potential reduce by 109.4 kB

  • Original 1.1 MB
  • After minification 1.0 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. Tigule images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 19.1 kB

  • Original 296.9 kB
  • After minification 296.9 kB
  • After compression 277.8 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

-6%

Potential reduce by 7.2 kB

  • Original 123.5 kB
  • After minification 123.5 kB
  • After compression 116.3 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. Tigule.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 54 (67%)

Requests Now

81

After Optimization

27

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

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

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.

Best Practices

tigule.com best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

tigule.com SEO score

93

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tigule.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 Tigule.com 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 Tigule. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: