Tools & Wizards About Us
digicard.pk screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

digicard.pk

Digital Visting Card | Digital Mini Website | Create Your Digital Visiting Card Just 1500 PKR Digital Visiting Card | Online Business Card

Page Load Speed

4.5 sec in total

First Response

276 ms

Resources Loaded

2.8 sec

Page Rendered

1.4 sec

digicard.pk screenshot

About Website

Click here to check amazing Digi Card content for Pakistan. Otherwise, check out these important facts you probably never knew about digicard.pk

Best digital visiting card online with many designs, Now create in just 5 minutes and get it instantly.

Visit digicard.pk

Key Findings

We analyzed Digicard.pk page load time and found that the first response time was 276 ms and then it took 4.2 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

digicard.pk performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value19.8 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value1,660 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.035

100/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

Network Requests Diagram

digicard.pk

276 ms

digicard.pk

432 ms

adsbygoogle.js

105 ms

all.css

101 ms

awesome.min.css

197 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 64% of them (47 requests) were addressed to the original Digicard.pk, 14% (10 requests) were made to Fonts.gstatic.com and 7% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Digicard.pk.

Page Optimization Overview & Recommendations

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

Content Size

22.8 MB

After Optimization

20.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Digicard.pk main page is 22.8 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. Only a small number of websites need less resources to load. Images take 22.3 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 18.0 kB

  • Original 25.2 kB
  • After minification 23.0 kB
  • After compression 7.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 18.0 kB or 72% of the original size.

Image Optimization

-10%

Potential reduce by 2.1 MB

  • Original 22.3 MB
  • After minification 20.2 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. Digi Card images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.3 kB

  • Original 398.3 kB
  • After minification 398.3 kB
  • After compression 395.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

-1%

Potential reduce by 1.2 kB

  • Original 85.1 kB
  • After minification 85.1 kB
  • After compression 83.9 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. Digicard.pk has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (23%)

Requests Now

61

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

digicard.pk

digicard.pk

276 ms

digicard.pk

digicard.pk

432 ms

adsbygoogle.js

adsbygoogle.js

105 ms

all.css

all.css

101 ms

awesome.min.css

awesome.min.css

197 ms

icon

icon

34 ms

css

css

47 ms

css2.css

css2.css

289 ms

mobile_css.css

mobile_css.css

292 ms

master_js.js

master_js.js

400 ms

show_ads_impl.js

show_ads_impl.js

402 ms

zrt_lookup.html

zrt_lookup.html

23 ms

css

css

15 ms

css2

css2

17 ms

logo.png

logo.png

340 ms

back5.png

back5.png

1015 ms

template3.png

template3.png

618 ms

template4.png

template4.png

1063 ms

template2.png

template2.png

1079 ms

template7.png

template7.png

1058 ms

wtsp.png

wtsp.png

618 ms

template31.png

template31.png

793 ms

template32.png

template32.png

1011 ms

template33.png

template33.png

871 ms

template34.png

template34.png

1011 ms

template35.png

template35.png

1228 ms

template1.png

template1.png

1070 ms

template5.png

template5.png

1107 ms

template6.png

template6.png

1250 ms

template8.png

template8.png

1163 ms

template9.png

template9.png

1268 ms

template10.png

template10.png

1276 ms

template11.png

template11.png

1203 ms

template12.png

template12.png

1361 ms

template13.png

template13.png

1301 ms

template29.png

template29.png

1320 ms

template30.png

template30.png

1348 ms

template14.png

template14.png

1369 ms

template15.png

template15.png

1376 ms

template16.png

template16.png

1398 ms

template17.png

template17.png

1415 ms

template18.png

template18.png

1447 ms

template19.png

template19.png

1461 ms

template20.png

template20.png

1470 ms

template21.png

template21.png

1475 ms

template22.png

template22.png

1494 ms

template23.png

template23.png

1509 ms

template24.png

template24.png

1546 ms

template25.png

template25.png

1562 ms

_h9_z69LZFQ

_h9_z69LZFQ

210 ms

template26.png

template26.png

1532 ms

LYjYdG7kmE0gV69VVPPdFl06VN9JG7Sy.ttf

LYjYdG7kmE0gV69VVPPdFl06VN9JG7Sy.ttf

80 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

81 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

119 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

129 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

130 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

157 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

173 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

173 ms

ads

ads

131 ms

www-player.css

www-player.css

61 ms

www-embed-player.js

www-embed-player.js

94 ms

base.js

base.js

166 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1203 ms

ad_status.js

ad_status.js

183 ms

template27.png

template27.png

986 ms

embed.js

embed.js

38 ms

template28.png

template28.png

848 ms

id

id

30 ms

business.png

business.png

858 ms

Create

Create

66 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

10 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

10 ms

GenerateIT

GenerateIT

15 ms

Accessibility Review

digicard.pk accessibility score

53

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

digicard.pk best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Page has valid source maps

SEO Factors

digicard.pk SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Digicard.pk can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Digicard.pk 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

digicard.pk

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