Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

digilant.com

Digital Media Strategy & Buying Partner | Digilant

Page Load Speed

1.2 sec in total

First Response

60 ms

Resources Loaded

672 ms

Page Rendered

487 ms

digilant.com screenshot

About Website

Welcome to digilant.com homepage info - get ready to check Digilant best content for India right away, or after learning these important things about digilant.com

Digilant's digital marketing expertise helps brands & agencies alike drive results & make an impact. From media planning to reporting & insights, we got you covered!

Visit digilant.com

Key Findings

We analyzed Digilant.com page load time and found that the first response time was 60 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

digilant.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value8.8 s

15/100

10%

TBT (Total Blocking Time)

Value2,180 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.059

98/100

15%

TTI (Time to Interactive)

Value19.7 s

2/100

10%

Network Requests Diagram

digilant.com

60 ms

digilant.com

118 ms

font-awesome.min.css

31 ms

owl.carousel.min.css

39 ms

owl.theme.default.min.css

45 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 68% of them (21 requests) were addressed to the original Digilant.com, 26% (8 requests) were made to Cdnjs.cloudflare.com and 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (387 ms) relates to the external source Digilantstg.wpengine.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 48.5 kB (27%)

Content Size

182.7 kB

After Optimization

134.2 kB

In fact, the total size of Digilant.com main page is 182.7 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. 50% of websites need less resources to load. Javascripts take 69.1 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 47.0 kB

  • Original 62.4 kB
  • After minification 59.7 kB
  • After compression 15.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. 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 47.0 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 21.5 kB
  • After minification 21.5 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. Digilant images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 71 B

  • Original 69.1 kB
  • After minification 69.1 kB
  • After compression 69.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

-5%

Potential reduce by 1.4 kB

  • Original 29.7 kB
  • After minification 29.7 kB
  • After compression 28.3 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. Digilant.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (58%)

Requests Now

26

After Optimization

11

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

Accessibility Review

digilant.com accessibility score

78

Accessibility Issues

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

digilant.com 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

SEO Factors

digilant.com SEO score

79

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

High

Image elements do not have [alt] attributes

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

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

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