Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

pilog.in

Digital Transformation | Master Data Management Solution| Pilog Group

Page Load Speed

2.5 sec in total

First Response

192 ms

Resources Loaded

1.9 sec

Page Rendered

404 ms

pilog.in screenshot

About Website

Visit pilog.in now to see the best up-to-date Pilog content for South Africa and also check out these interesting facts you probably never knew about pilog.in

PiLog Group provides, Digital Transformation & Master Data Management Solution, we blend our technology and industry expertise to develop solutions to help organizations create engaging digital experi...

Visit pilog.in

Key Findings

We analyzed Pilog.in page load time and found that the first response time was 192 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

pilog.in performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value23.3 s

0/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value4,490 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.432

22/100

15%

TTI (Time to Interactive)

Value20.9 s

1/100

10%

Network Requests Diagram

pilog.in

192 ms

www.piloggroup.com

76 ms

bootstrap.min.css

37 ms

font-awesome.css

51 ms

icomoon.css

48 ms

Our browser made a total of 264 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Pilog.in, 88% (231 requests) were made to Piloggroup.com and 3% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (754 ms) relates to the external source Piloggroup.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 285.2 kB (6%)

Content Size

4.9 MB

After Optimization

4.6 MB

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

HTML Optimization

-89%

Potential reduce by 254.2 kB

  • Original 284.1 kB
  • After minification 190.6 kB
  • After compression 30.0 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. This page needs HTML code to be minified as it can gain 93.5 kB, which is 33% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 254.2 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 9.6 kB

  • Original 4.3 MB
  • After minification 4.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. Pilog images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 13.8 kB

  • Original 182.0 kB
  • After minification 182.0 kB
  • After compression 168.2 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

-8%

Potential reduce by 7.7 kB

  • Original 91.3 kB
  • After minification 91.3 kB
  • After compression 83.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. Pilog.in has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 48 (20%)

Requests Now

246

After Optimization

198

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

Accessibility Review

pilog.in accessibility score

61

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

pilog.in best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

pilog.in SEO score

79

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pilog.in 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 Pilog.in 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 Pilog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: