Tools & Wizards About Us
lawazem.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

lawazem.com

LAWAZEM

Page Load Speed

4.7 sec in total

First Response

835 ms

Resources Loaded

3.2 sec

Page Rendered

618 ms

lawazem.com screenshot

About Website

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

LAWAZEM the first B2B eCommerce platform for all your company's operational Procurement needs, from grocery to stationery to cleaning to printing , and more.

Visit lawazem.com

Key Findings

We analyzed Lawazem.com page load time and found that the first response time was 835 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

lawazem.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value15.9 s

0/100

25%

SI (Speed Index)

Value13.3 s

2/100

10%

TBT (Total Blocking Time)

Value3,010 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.152

75/100

15%

TTI (Time to Interactive)

Value18.9 s

3/100

10%

Network Requests Diagram

lawazem.com

835 ms

js

99 ms

formidableforms.css

217 ms

icons.css

207 ms

global.css

211 ms

Our browser made a total of 133 requests to load all elements on the main page. We found that 74% of them (99 requests) were addressed to the original Lawazem.com, 15% (20 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (931 ms) belongs to the original domain Lawazem.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 186.7 kB (5%)

Content Size

3.9 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lawazem.com main page is 3.9 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. 80% 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 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 141.7 kB

  • Original 212.5 kB
  • After minification 206.0 kB
  • After compression 70.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 141.7 kB or 67% of the original size.

Image Optimization

-1%

Potential reduce by 31.3 kB

  • Original 3.3 MB
  • After minification 3.3 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. LAWAZEM images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 4.3 kB

  • Original 203.2 kB
  • After minification 203.2 kB
  • After compression 198.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

-5%

Potential reduce by 9.5 kB

  • Original 200.9 kB
  • After minification 200.6 kB
  • After compression 191.4 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. Lawazem.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 68 (72%)

Requests Now

95

After Optimization

27

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lawazem.com

lawazem.com

835 ms

js

js

99 ms

formidableforms.css

formidableforms.css

217 ms

icons.css

icons.css

207 ms

global.css

global.css

211 ms

livechat-icons.css

livechat-icons.css

213 ms

style.min.css

style.min.css

211 ms

if-menu-site.css

if-menu-site.css

213 ms

header-footer-elementor.css

header-footer-elementor.css

312 ms

elementor-icons.min.css

elementor-icons.min.css

320 ms

frontend.min.css

frontend.min.css

303 ms

swiper.min.css

swiper.min.css

311 ms

post-481.css

post-481.css

335 ms

frontend.min.css

frontend.min.css

359 ms

all.min.css

all.min.css

430 ms

v4-shims.min.css

v4-shims.min.css

423 ms

post-483.css

post-483.css

425 ms

frontend.css

frontend.css

471 ms

livechat-contact-button.css

livechat-contact-button.css

482 ms

livechat-quality-badge.css

livechat-quality-badge.css

506 ms

post-554.css

post-554.css

534 ms

post-1343.css

post-1343.css

549 ms

cms-navigation-base.css

cms-navigation-base.css

583 ms

cms-navigation.css

cms-navigation.css

621 ms

v4-shims.css

v4-shims.css

592 ms

all.css

all.css

661 ms

app.css

app.css

682 ms

style.css

style.css

706 ms

css

css

46 ms

fontawesome.min.css

fontawesome.min.css

720 ms

solid.min.css

solid.min.css

627 ms

regular.min.css

regular.min.css

775 ms

brands.min.css

brands.min.css

777 ms

language-cookie.js

language-cookie.js

808 ms

frontend-gtag.min.js

frontend-gtag.min.js

843 ms

v4-shims.min.js

v4-shims.min.js

837 ms

jquery.min.js

jquery.min.js

836 ms

jquery-migrate.min.js

jquery-migrate.min.js

931 ms

contact-button.js

contact-button.js

130 ms

quality-badge.js

quality-badge.js

472 ms

js

js

129 ms

js

js

128 ms

widget.js

widget.js

39 ms

widget.js

widget.js

225 ms

post-1628.css

post-1628.css

898 ms

animations.min.css

animations.min.css

786 ms

email-decode.min.js

email-decode.min.js

636 ms

waypoints.min.js

waypoints.min.js

783 ms

frontend.js

frontend.js

813 ms

themo-foot.js

themo-foot.js

780 ms

vendor_footer.js

vendor_footer.js

894 ms

main.js

main.js

805 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

884 ms

webpack.runtime.min.js

webpack.runtime.min.js

802 ms

frontend-modules.min.js

frontend-modules.min.js

792 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

776 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

905 ms

wp-polyfill.min.js

wp-polyfill.min.js

861 ms

hooks.min.js

hooks.min.js

883 ms

i18n.min.js

i18n.min.js

878 ms

frontend.min.js

frontend.min.js

834 ms

core.min.js

core.min.js

828 ms

frontend.min.js

frontend.min.js

929 ms

elements-handlers.min.js

elements-handlers.min.js

901 ms

underscore.min.js

underscore.min.js

887 ms

wp-util.min.js

wp-util.min.js

862 ms

frontend.min.js

frontend.min.js

849 ms

js

js

165 ms

Untitlssed-5-2.png

Untitlssed-5-2.png

501 ms

ar-flag.svg

ar-flag.svg

565 ms

App-Store-241x80.png

App-Store-241x80.png

570 ms

Google-Play-241x80.png

Google-Play-241x80.png

571 ms

Layer_1-1.svg

Layer_1-1.svg

599 ms

Group-1-1-min.png

Group-1-1-min.png

678 ms

worker-operating-forklift-machine-relocating-goods-large-warehouse-center-1-1-min.png

worker-operating-forklift-machine-relocating-goods-large-warehouse-center-1-1-min.png

753 ms

Group-503-1.svg

Group-503-1.svg

683 ms

image-11.png

image-11.png

694 ms

Button-container.png

Button-container.png

694 ms

Button-container-1.png

Button-container-1.png

711 ms

Button-container-2.png

Button-container-2.png

839 ms

Button-container-3.png

Button-container-3.png

792 ms

Switch-container.png

Switch-container.png

749 ms

Group-509-1-min.png

Group-509-1-min.png

908 ms

brochure-1.png

brochure-1.png

786 ms

Group-511-21nrojrjpjpqscveqqyniem30k2rzaegxfum2xf0zk1m.png

Group-511-21nrojrjpjpqscveqqyniem30k2rzaegxfum2xf0zk1m.png

850 ms

S6uyw4BMUTPHjx4wWCWtFCc.woff

S6uyw4BMUTPHjx4wWCWtFCc.woff

827 ms

js

js

115 ms

S6uyw4BMUTPHjxAwWCWtFCfQ7A.woff

S6uyw4BMUTPHjxAwWCWtFCfQ7A.woff

839 ms

S6u9w4BMUTPHh7USSwiPHw3q5d0.woff

S6u9w4BMUTPHh7USSwiPHw3q5d0.woff

792 ms

S6u9w4BMUTPHh7USSwaPHw3q5d0N7w.woff

S6u9w4BMUTPHh7USSwaPHw3q5d0N7w.woff

792 ms

S6u9w4BMUTPHh6UVSwiPHw3q5d0.woff

S6u9w4BMUTPHh6UVSwiPHw3q5d0.woff

872 ms

S6u9w4BMUTPHh6UVSwaPHw3q5d0N7w.woff

S6u9w4BMUTPHh6UVSwaPHw3q5d0N7w.woff

843 ms

SomarSans-Bold.ttf

SomarSans-Bold.ttf

81 ms

SomarSans-SemiBold.ttf

SomarSans-SemiBold.ttf

81 ms

SomarSans-Regular.ttf

SomarSans-Regular.ttf

81 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

199 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

204 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

205 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

201 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

205 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

204 ms

fa-solid-900.woff

fa-solid-900.woff

907 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hOA-a1PiKQ.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hOA-a1PiKQ.ttf

203 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hNI-a1PiKQ.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hNI-a1PiKQ.ttf

264 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hL4-a1PiKQ.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hL4-a1PiKQ.ttf

205 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hGA-a1PiKQ.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hGA-a1PiKQ.ttf

263 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hD45a1PiKQ.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hD45a1PiKQ.ttf

206 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hAc5a1PiKQ.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hAc5a1PiKQ.ttf

204 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hGA5a1PiKQ.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hGA5a1PiKQ.ttf

263 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hEk5a1PiKQ.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hEk5a1PiKQ.ttf

264 ms

KFOkCnqEu92Fr1Mu51xIIzc.ttf

KFOkCnqEu92Fr1Mu51xIIzc.ttf

268 ms

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

264 ms

KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf

KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf

267 ms

KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf

KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf

268 ms

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

263 ms

KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf

KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf

266 ms

fa-solid-900.woff

fa-solid-900.woff

874 ms

tracking.js

tracking.js

110 ms

fa-regular-400.woff

fa-regular-400.woff

717 ms

fa-regular-400.woff

fa-regular-400.woff

717 ms

fa-brands-400.woff

fa-brands-400.woff

790 ms

fa-brands-400.woff

fa-brands-400.woff

790 ms

linea-basic-10.woff

linea-basic-10.woff

882 ms

travelpack.svg

travelpack.svg

882 ms

travelpack.woff

travelpack.woff

709 ms

LAWAZEM-payment_logos-768x81.png

LAWAZEM-payment_logos-768x81.png

750 ms

App-Store-1-1-241x80.png

App-Store-1-1-241x80.png

806 ms

Google-Play-1-1-241x80.png

Google-Play-1-1-241x80.png

811 ms

linkedin-logo-1-1-1-1.svg

linkedin-logo-1-1-1-1.svg

823 ms

social-1.png

social-1.png

771 ms

LAWAZEM-vat_logo.png

LAWAZEM-vat_logo.png

758 ms

Layer_1-1024x107.png

Layer_1-1024x107.png

771 ms

main.js

main.js

103 ms

Accessibility Review

lawazem.com accessibility score

78

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

SEO Factors

lawazem.com SEO score

76

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

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

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

lawazem.com

Open Graph data is detected on the main page of LAWAZEM. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: