Tools & Wizards About Us
zapp.today screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

zapp.today

ZAPP TODAY - The Best Delivery Service In Kathmandu, Nepal

Page Load Speed

6.7 sec in total

First Response

148 ms

Resources Loaded

6.1 sec

Page Rendered

428 ms

zapp.today screenshot

About Website

Welcome to zapp.today homepage info - get ready to check ZAPP best content right away, or after learning these important things about zapp.today

ZAPP TODAY, a delivery & courier service in Kathmandu, Nepal. Providing service for personal & business deliveries through on-demand and multistop deliveries.

Visit zapp.today

Key Findings

We analyzed Zapp.today page load time and found that the first response time was 148 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

zapp.today performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value5.3 s

59/100

10%

TBT (Total Blocking Time)

Value560 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.3

39/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

zapp.today

148 ms

zapp.today

371 ms

js

134 ms

style.css

86 ms

style.min.css

102 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 43% of them (44 requests) were addressed to the original Zapp.today, 17% (18 requests) were made to Fonts.gstatic.com and 16% (16 requests) were made to C0.wp.com. The less responsive or slowest element that took the longest time to load (4.8 sec) relates to the external source I0.wp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 177.1 kB (8%)

Content Size

2.2 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Zapp.today main page is 2.2 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. 70% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 103.1 kB

  • Original 123.9 kB
  • After minification 119.8 kB
  • After compression 20.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. 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 103.1 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 27 B

  • Original 1.6 MB
  • After minification 1.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. ZAPP images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 23.6 kB

  • Original 254.7 kB
  • After minification 254.7 kB
  • After compression 231.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

-18%

Potential reduce by 50.3 kB

  • Original 274.0 kB
  • After minification 274.0 kB
  • After compression 223.7 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. Zapp.today needs all CSS files to be minified and compressed as it can save up to 50.3 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (77%)

Requests Now

82

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

zapp.today

zapp.today

148 ms

zapp.today

zapp.today

371 ms

js

js

134 ms

style.css

style.css

86 ms

style.min.css

style.min.css

102 ms

style.min.css

style.min.css

113 ms

style.min.css

style.min.css

108 ms

style.min.css

style.min.css

119 ms

style.min.css

style.min.css

118 ms

style.min.css

style.min.css

117 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

118 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

125 ms

styles.css

styles.css

230 ms

mailerlite_forms.css

mailerlite_forms.css

246 ms

css

css

122 ms

font-awesome.min.css

font-awesome.min.css

246 ms

jquery-ui.css

jquery-ui.css

248 ms

simple-job-board-public.css

simple-job-board-public.css

312 ms

editor.css

editor.css

243 ms

header-footer-elementor.css

header-footer-elementor.css

295 ms

elementor-icons.min.css

elementor-icons.min.css

315 ms

frontend.min.css

frontend.min.css

384 ms

post-8.css

post-8.css

316 ms

post-159.css

post-159.css

316 ms

frontend.css

frontend.css

362 ms

post-160.css

post-160.css

379 ms

post-184.css

post-184.css

377 ms

style.min.css

style.min.css

380 ms

theme.min.css

theme.min.css

381 ms

header-footer.min.css

header-footer.min.css

431 ms

ekiticons.css

ekiticons.css

449 ms

widget-styles.css

widget-styles.css

649 ms

responsive.css

responsive.css

458 ms

css

css

151 ms

fontawesome.min.css

fontawesome.min.css

513 ms

brands.min.css

brands.min.css

456 ms

solid.min.css

solid.min.css

497 ms

regular.min.css

regular.min.css

516 ms

jetpack.css

jetpack.css

109 ms

jquery.min.js

jquery.min.js

116 ms

jquery-migrate.min.js

jquery-migrate.min.js

114 ms

frontend-gtag.min.js

frontend-gtag.min.js

516 ms

reading-progress.min.css

reading-progress.min.css

514 ms

animations.min.css

animations.min.css

563 ms

photon.min.js

photon.min.js

112 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

113 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

114 ms

wp-polyfill.min.js

wp-polyfill.min.js

115 ms

index.js

index.js

577 ms

frontend-script.js

frontend-script.js

583 ms

widget-scripts.js

widget-scripts.js

792 ms

frontend.js

frontend.js

592 ms

reading-progress.min.js

reading-progress.min.js

630 ms

webpack.runtime.min.js

webpack.runtime.min.js

785 ms

core.min.js

core.min.js

113 ms

e-202410.js

e-202410.js

111 ms

frontend-modules.min.js

frontend-modules.min.js

785 ms

waypoints.min.js

waypoints.min.js

718 ms

analytics.js

analytics.js

27 ms

frontend.min.js

frontend.min.js

631 ms

linkid.js

linkid.js

9 ms

collect

collect

13 ms

animate-circle.js

animate-circle.js

575 ms

elementor.js

elementor.js

560 ms

swiper.min.js

swiper.min.js

680 ms

collect

collect

95 ms

universal.js

universal.js

271 ms

fbevents.js

fbevents.js

173 ms

ZAPP_Today_Logo_200x65.png

ZAPP_Today_Logo_200x65.png

265 ms

Banner-1.png

Banner-1.png

152 ms

Scooter-Delivery-Mockup-scaled.jpg

Scooter-Delivery-Mockup-scaled.jpg

303 ms

ZAPP_Bike-Mockup_NoShadow.png

ZAPP_Bike-Mockup_NoShadow.png

4500 ms

iPhone13_MockUp.png

iPhone13_MockUp.png

4815 ms

ZAPP_iPhone12.png

ZAPP_iPhone12.png

666 ms

iPhone-11-Pro-Smartphone-Mockups-004.png

iPhone-11-Pro-Smartphone-Mockups-004.png

776 ms

scooter.png

scooter.png

697 ms

activity.png

activity.png

941 ms

delivery-man.png

delivery-man.png

1342 ms

notification.png

notification.png

1393 ms

Phone-App-Screen-Mockup-PSD-03.png

Phone-App-Screen-Mockup-PSD-03.png

2938 ms

app-store-black.png

app-store-black.png

1324 ms

google-play-black.png

google-play-black.png

1705 ms

xfbml.customerchat.js

xfbml.customerchat.js

138 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

172 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

209 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

229 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

229 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

228 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

227 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

228 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

227 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

261 ms

QdVUSTchPBm7nuUeVf70viFg.ttf

QdVUSTchPBm7nuUeVf70viFg.ttf

262 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3ig.ttf

262 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDIkhdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDIkhdTQ3ig.ttf

261 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTQ3ig.ttf

261 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDDshdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDDshdTQ3ig.ttf

261 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTQ3ig.ttf

264 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3ig.ttf

263 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDDsmdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDDsmdTQ3ig.ttf

264 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDBImdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDBImdTQ3ig.ttf

264 ms

fa-brands-400.woff

fa-brands-400.woff

294 ms

100 ms

Accessibility Review

zapp.today accessibility score

83

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

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

zapp.today 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

zapp.today SEO score

88

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

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 Zapp.today 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 Zapp.today 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

zapp.today

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