Tools & Wizards About Us
nilogy.com screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

nilogy.com

متجر إلكتروني مجاني - ترينافو

Page Load Speed

3.3 sec in total

First Response

47 ms

Resources Loaded

2.3 sec

Page Rendered

982 ms

nilogy.com screenshot

About Website

Click here to check amazing Nilogy content for Sudan. Otherwise, check out these important facts you probably never knew about nilogy.com

إذا كنت تريد إنشاء متجر إلكتروني بتصميمات جذابة وعصرية ، فإن TrinavoShops  هي الاختيار الأمثل. نقدم لك في TrinavoShops ،كل ما تحتاج إليه لتأسيس متجرك

Visit nilogy.com

Key Findings

We analyzed Nilogy.com page load time and found that the first response time was 47 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

nilogy.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value1,170 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.211

59/100

15%

TTI (Time to Interactive)

Value9.0 s

33/100

10%

Network Requests Diagram

nilogy.com

47 ms

nilogy.com

76 ms

trinavo.com

168 ms

jquery.min.js

24 ms

trp-language-cookie.js

47 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Nilogy.com, 67% (56 requests) were made to Trinavo.com and 20% (17 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (171 ms) relates to the external source Trinavo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 258.1 kB (36%)

Content Size

707.1 kB

After Optimization

449.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nilogy.com main page is 707.1 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. 70% of websites need less resources to load. HTML takes 309.0 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 257.3 kB

  • Original 309.0 kB
  • After minification 308.9 kB
  • After compression 51.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 257.3 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 5 B

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

JavaScript Optimization

-0%

Potential reduce by 378 B

  • Original 238.2 kB
  • After minification 238.2 kB
  • After compression 237.8 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

-0%

Potential reduce by 351 B

  • Original 111.8 kB
  • After minification 111.7 kB
  • After compression 111.4 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. Nilogy.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 52 (88%)

Requests Now

59

After Optimization

7

  • Images
  • JavaScript
  • CSS

The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nilogy. 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 27 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

nilogy.com

nilogy.com

47 ms

nilogy.com

nilogy.com

76 ms

trinavo.com

trinavo.com

168 ms

jquery.min.js

jquery.min.js

24 ms

trp-language-cookie.js

trp-language-cookie.js

47 ms

v4-shims.min.js

v4-shims.min.js

53 ms

js

js

110 ms

css

css

97 ms

widget-icon-box-rtl.min.css

widget-icon-box-rtl.min.css

74 ms

widget-icon-list.min.css

widget-icon-list.min.css

73 ms

addthis_widget.js

addthis_widget.js

157 ms

frontend.min.js

frontend.min.js

93 ms

app.js

app.js

93 ms

dom-ready.min.js

dom-ready.min.js

91 ms

main.js

main.js

92 ms

googlesitekit-consent-mode-3d6495dceaebc28bcca3.js

googlesitekit-consent-mode-3d6495dceaebc28bcca3.js

92 ms

ar.js

ar.js

93 ms

frontend.js

frontend.js

138 ms

trp-clickable-ls.js

trp-clickable-ls.js

103 ms

e-202432.js

e-202432.js

92 ms

webpack.runtime.min.js

webpack.runtime.min.js

103 ms

frontend-modules.min.js

frontend-modules.min.js

134 ms

waypoints.min.js

waypoints.min.js

136 ms

core.min.js

core.min.js

135 ms

frontend.min.js

frontend.min.js

137 ms

underscore.min.js

underscore.min.js

137 ms

wp-util.min.js

wp-util.min.js

138 ms

frontend.min.js

frontend.min.js

139 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

139 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

142 ms

main.js

main.js

139 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

142 ms

logo.webp

logo.webp

171 ms

ar.png

ar.png

80 ms

en_US.png

en_US.png

79 ms

shoper-1BjsO2t42_4-unsplash-768x512.webp

shoper-1BjsO2t42_4-unsplash-768x512.webp

80 ms

zakra-invite-image.jpg

zakra-invite-image.jpg

81 ms

fbevents.js

fbevents.js

45 ms

style-block.css

style-block.css

14 ms

normal.woff2

normal.woff2

162 ms

normal.woff2

normal.woff2

156 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hOA-a1PiKQ.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hOA-a1PiKQ.ttf

40 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hNI-a1PiKQ.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hNI-a1PiKQ.ttf

70 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hL4-a1PiKQ.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hL4-a1PiKQ.ttf

101 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hGA-a1PiKQ.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hGA-a1PiKQ.ttf

107 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hD45a1PiKQ.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hD45a1PiKQ.ttf

107 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hAc5a1PiKQ.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hAc5a1PiKQ.ttf

107 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hGA5a1PiKQ.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hGA5a1PiKQ.ttf

106 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hEk5a1PiKQ.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hEk5a1PiKQ.ttf

106 ms

main.min-rtl.css

main.min-rtl.css

17 ms

main.css

main.css

24 ms

everest-forms-rtl.css

everest-forms-rtl.css

25 ms

intlTelInput.css

intlTelInput.css

22 ms

frontend.css

frontend.css

34 ms

frontend.css

frontend.css

22 ms

styles.css

styles.css

25 ms

trp-language-switcher.css

trp-language-switcher.css

42 ms

Lato-Bold.woff

Lato-Bold.woff

75 ms

Lato-Regular.woff

Lato-Regular.woff

93 ms

trp-popup.css

trp-popup.css

14 ms

frontend.css

frontend.css

22 ms

font-awesome.min.css

font-awesome.min.css

56 ms

css2

css2

16 ms

frontend-lite-rtl.min.css

frontend-lite-rtl.min.css

18 ms

swiper.min.css

swiper.min.css

66 ms

post-5756.css

post-5756.css

23 ms

all.min.css

all.min.css

24 ms

v4-shims.min.css

v4-shims.min.css

24 ms

font-awesome.min.css

font-awesome.min.css

24 ms

animate.css

animate.css

28 ms

style.css

style.css

49 ms

responsive.css

responsive.css

29 ms

post-6347.css

post-6347.css

24 ms

animations.min.css

animations.min.css

94 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

41 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

38 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

38 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

40 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

40 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

40 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

42 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

42 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

42 ms

Accessibility Review

nilogy.com accessibility score

98

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.

Best Practices

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

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

    AR

  • Language Claimed

    AR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nilogy.com can be misinterpreted by Google and other search engines. Our service has detected that Arabic is used on the page, and it matches the claimed language. Our system also found out that Nilogy.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

nilogy.com

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