Tools & Wizards About Us
taza.sa screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

taza.sa

Taza Broast

Page Load Speed

4.1 sec in total

First Response

312 ms

Resources Loaded

3.1 sec

Page Rendered

649 ms

taza.sa screenshot

About Website

Visit taza.sa now to see the best up-to-date Taza content and also check out these interesting facts you probably never knew about taza.sa

Taza Broast

Visit taza.sa

Key Findings

We analyzed Taza.sa page load time and found that the first response time was 312 ms and then it took 3.8 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

taza.sa performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value33.2 s

0/100

25%

SI (Speed Index)

Value19.0 s

0/100

10%

TBT (Total Blocking Time)

Value730 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value21.4 s

1/100

10%

Network Requests Diagram

taza.sa

312 ms

taza.sa

296 ms

css

31 ms

css2

49 ms

bootstrap.min.css

244 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 85% of them (50 requests) were addressed to the original Taza.sa, 7% (4 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Taza.sa.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.1 MB (31%)

Content Size

6.7 MB

After Optimization

4.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Taza.sa main page is 6.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. 40% of websites need less resources to load. Images take 6.3 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 82.6 kB

  • Original 91.0 kB
  • After minification 42.6 kB
  • After compression 8.4 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 48.4 kB, which is 53% 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 82.6 kB or 91% of the original size.

Image Optimization

-30%

Potential reduce by 1.9 MB

  • Original 6.3 MB
  • After minification 4.4 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. Obviously, Taza needs image optimization as it can save up to 1.9 MB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-27%

Potential reduce by 44.1 kB

  • Original 165.9 kB
  • After minification 165.9 kB
  • After compression 121.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 44.1 kB or 27% of the original size.

CSS Optimization

-50%

Potential reduce by 102.6 kB

  • Original 205.2 kB
  • After minification 205.2 kB
  • After compression 102.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. Taza.sa needs all CSS files to be minified and compressed as it can save up to 102.6 kB or 50% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (42%)

Requests Now

53

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

taza.sa

taza.sa

312 ms

taza.sa

taza.sa

296 ms

css

css

31 ms

css2

css2

49 ms

bootstrap.min.css

bootstrap.min.css

244 ms

font-awesome.min.css

font-awesome.min.css

188 ms

plugins.css

plugins.css

199 ms

style-main.css

style-main.css

337 ms

responsive.css

responsive.css

190 ms

modernizr-custom.js

modernizr-custom.js

186 ms

pluginStyle.css

pluginStyle.css

375 ms

jquery.min.js

jquery.min.js

474 ms

bootstrap.min.js

bootstrap.min.js

375 ms

plugins.js

plugins.js

376 ms

scripts.js

scripts.js

537 ms

settings.css

settings.css

561 ms

layers.css

layers.css

622 ms

navigation.css

navigation.css

628 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

683 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

675 ms

CTA_BGIMAGE1_105.png

CTA_BGIMAGE1_105.png

581 ms

ar.jpg

ar.jpg

410 ms

HP_IMAGENAME_178.jpg

HP_IMAGENAME_178.jpg

819 ms

HP_IMAGENAME_155.jpg

HP_IMAGENAME_155.jpg

870 ms

HP_IMAGENAME_156.jpg

HP_IMAGENAME_156.jpg

966 ms

HP_IMAGENAME_154.jpg

HP_IMAGENAME_154.jpg

883 ms

HP_IMAGENAME_153.jpg

HP_IMAGENAME_153.jpg

938 ms

MDL_IMAGE1_199.jpg

MDL_IMAGE1_199.jpg

1046 ms

MDL_IMAGE1_119.jpg

MDL_IMAGE1_119.jpg

1175 ms

MDL_IMAGE1_107.jpg

MDL_IMAGE1_107.jpg

1222 ms

C_HEADERIMAGE_130.jpg

C_HEADERIMAGE_130.jpg

1117 ms

C_HEADERIMAGE_127.jpg

C_HEADERIMAGE_127.jpg

1175 ms

C_HEADERIMAGE_129.jpg

C_HEADERIMAGE_129.jpg

1200 ms

C_HEADERIMAGE_128.jpg

C_HEADERIMAGE_128.jpg

1284 ms

C_HEADERIMAGE_131.jpg

C_HEADERIMAGE_131.jpg

1299 ms

C_HEADERIMAGE_144.jpg

C_HEADERIMAGE_144.jpg

1353 ms

NE_MAINIMAGE_19.jpg

NE_MAINIMAGE_19.jpg

1529 ms

NE_MAINIMAGE_12.jpg

NE_MAINIMAGE_12.jpg

1579 ms

CTA_BGIMAGE1_116.png

CTA_BGIMAGE1_116.png

1641 ms

CTA_BGIMAGE1_79.png

CTA_BGIMAGE1_79.png

1704 ms

CTA_BGIMAGE1_106.png

CTA_BGIMAGE1_106.png

1706 ms

css

css

19 ms

css

css

36 ms

sdk.js

sdk.js

79 ms

bg.jpg

bg.jpg

1573 ms

010.jpg

010.jpg

1840 ms

googleplay.png

googleplay.png

1712 ms

itunes.png

itunes.png

1752 ms

snapchat.png

snapchat.png

1779 ms

tiktok.png

tiktok.png

1843 ms

font

font

52 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1894 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

1880 ms

font

font

274 ms

sdk.js

sdk.js

11 ms

44 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

1620 ms

owl.carousel.min.css

owl.carousel.min.css

1642 ms

owl.theme.default.min.css

owl.theme.default.min.css

1701 ms

Accessibility Review

taza.sa accessibility score

89

Accessibility Issues

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

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

Links do not have a discernible name

Best Practices

taza.sa best practices score

58

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

taza.sa SEO score

81

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

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Taza.sa 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 Taza.sa 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

taza.sa

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