Tools & Wizards About Us
wekeep.co screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

wekeep.co

Wafeq – Accounting software for modern businesses | Wafeq

Page Load Speed

3.3 sec in total

First Response

185 ms

Resources Loaded

1.8 sec

Page Rendered

1.3 sec

wekeep.co screenshot

About Website

Click here to check amazing Wekeep content for United Arab Emirates. Otherwise, check out these important facts you probably never knew about wekeep.co

Send invoices or purchase orders, manage your inventory and your payroll, and get over 30 reports to manage your company, all in one software.

Visit wekeep.co

Key Findings

We analyzed Wekeep.co page load time and found that the first response time was 185 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

wekeep.co performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

61/100

25%

SI (Speed Index)

Value7.3 s

28/100

10%

TBT (Total Blocking Time)

Value7,940 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.099

90/100

15%

TTI (Time to Interactive)

Value21.6 s

1/100

10%

Network Requests Diagram

www.wafeq.com

185 ms

en

286 ms

32b714a6b0985e7c.css

142 ms

c7927b3f584b5b3c.css

165 ms

846225897da88520.css

113 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that all of those requests were addressed to Wekeep.co and no external sources were called. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Wafeq.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 401.8 kB (69%)

Content Size

584.0 kB

After Optimization

182.2 kB

  • HTML
  • Images

In fact, the total size of Wekeep.co main page is 584.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. HTML takes 453.0 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 398.9 kB

  • Original 453.0 kB
  • After minification 452.9 kB
  • After compression 54.2 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 398.9 kB or 88% of the original size.

Image Optimization

-2%

Potential reduce by 2.9 kB

  • Original 131.0 kB
  • After minification 128.0 kB

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

Requests Breakdown

Number of requests can be reduced by 31 (82%)

Requests Now

38

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.wafeq.com

www.wafeq.com

185 ms

en

en

286 ms

32b714a6b0985e7c.css

32b714a6b0985e7c.css

142 ms

c7927b3f584b5b3c.css

c7927b3f584b5b3c.css

165 ms

846225897da88520.css

846225897da88520.css

113 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

372 ms

webpack-d014c86442b8dfa3.js

webpack-d014c86442b8dfa3.js

121 ms

framework-aec4381329cec0e4.js

framework-aec4381329cec0e4.js

375 ms

main-402bc637b663a64b.js

main-402bc637b663a64b.js

374 ms

_app-3453f3ed91e90faf.js

_app-3453f3ed91e90faf.js

433 ms

ff4d53e7-8051945720a92c92.js

ff4d53e7-8051945720a92c92.js

378 ms

d0c16330-3cdb840a33459084.js

d0c16330-3cdb840a33459084.js

377 ms

252f366e-5515041b9f0feba2.js

252f366e-5515041b9f0feba2.js

376 ms

78e521c3-af92b3c152dc62b4.js

78e521c3-af92b3c152dc62b4.js

412 ms

1bfc9850-caca77da742790e5.js

1bfc9850-caca77da742790e5.js

378 ms

d3048c20-44e3fd4713f8c5d3.js

d3048c20-44e3fd4713f8c5d3.js

426 ms

d2094a0f-3b704b5b4b97bfb2.js

d2094a0f-3b704b5b4b97bfb2.js

423 ms

ee9ce975-6078dd6c8b223a9b.js

ee9ce975-6078dd6c8b223a9b.js

422 ms

1664-655c97a670cb5c27.js

1664-655c97a670cb5c27.js

465 ms

2943-1aa639d79344e516.js

2943-1aa639d79344e516.js

485 ms

4867-fe2b8b4cb33caf50.js

4867-fe2b8b4cb33caf50.js

857 ms

5675-c86cabc0286c995b.js

5675-c86cabc0286c995b.js

519 ms

4623-25bbd680eae0949b.js

4623-25bbd680eae0949b.js

582 ms

9304-6919358d6d593c56.js

9304-6919358d6d593c56.js

558 ms

2541-9d2be2a437e4d838.js

2541-9d2be2a437e4d838.js

657 ms

4140-9d81cdb17a0833de.js

4140-9d81cdb17a0833de.js

669 ms

7087-16064dc76cb143de.js

7087-16064dc76cb143de.js

646 ms

3860-9ece0b42513fa1ee.js

3860-9ece0b42513fa1ee.js

670 ms

9690-9ff6a04576322571.js

9690-9ff6a04576322571.js

706 ms

2642-06beebc78acb243a.js

2642-06beebc78acb243a.js

746 ms

1580-3d4cdea4ebb56184.js

1580-3d4cdea4ebb56184.js

783 ms

4332-62c50f4ada787a00.js

4332-62c50f4ada787a00.js

770 ms

4346-5d936c9581f6d87a.js

4346-5d936c9581f6d87a.js

772 ms

2562-2d53792b03511e34.js

2562-2d53792b03511e34.js

975 ms

%5BcountryLang%5D-3e74ca905f7cfa12.js

%5BcountryLang%5D-3e74ca905f7cfa12.js

846 ms

_buildManifest.js

_buildManifest.js

881 ms

_ssgManifest.js

_ssgManifest.js

880 ms

image

image

776 ms

image

image

1135 ms

image

image

717 ms

Accessibility Review

wekeep.co accessibility score

90

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

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

wekeep.co best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

wekeep.co SEO score

100

Search Engine Optimization Advices

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 Wekeep.co 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 Wekeep.co 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

wekeep.co

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