Tools & Wizards About Us
djinn.ca screenshot

Report Summary

  • 78

    Performance

    Renders faster than
    85% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

djinn.ca

Home Of Djinn - DJINN ANGELS AND DEMONS

Page Load Speed

1.5 sec in total

First Response

196 ms

Resources Loaded

556 ms

Page Rendered

778 ms

djinn.ca screenshot

About Website

Click here to check amazing DJINN content. Otherwise, check out these important facts you probably never knew about djinn.ca

<meta name="verifyownership" content="b5434b9837709a78a23377688612d349" />

Visit djinn.ca

Key Findings

We analyzed Djinn.ca page load time and found that the first response time was 196 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

djinn.ca performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

85/100

25%

SI (Speed Index)

Value2.8 s

95/100

10%

TBT (Total Blocking Time)

Value540 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

djinn.ca

196 ms

pluggables.css

13 ms

webs_common.js

16 ms

websover.min.js

15 ms

templatebase.css

17 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 12% of them (5 requests) were addressed to the original Djinn.ca, 24% (10 requests) were made to Static.websimages.com and 19% (8 requests) were made to Images.freewebs.com. The less responsive or slowest element that took the longest time to load (196 ms) belongs to the original domain Djinn.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 396.0 kB (59%)

Content Size

668.8 kB

After Optimization

272.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Djinn.ca main page is 668.8 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. 45% of websites need less resources to load. Javascripts take 346.9 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 22.6 kB

  • Original 32.6 kB
  • After minification 31.1 kB
  • After compression 10.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. 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 22.6 kB or 69% of the original size.

Image Optimization

-7%

Potential reduce by 5.8 kB

  • Original 86.6 kB
  • After minification 80.9 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. DJINN images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 220.4 kB

  • Original 346.9 kB
  • After minification 339.8 kB
  • After compression 126.5 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 220.4 kB or 64% of the original size.

CSS Optimization

-73%

Potential reduce by 147.2 kB

  • Original 202.6 kB
  • After minification 190.9 kB
  • After compression 55.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. Djinn.ca needs all CSS files to be minified and compressed as it can save up to 147.2 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (67%)

Requests Now

39

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

djinn.ca

djinn.ca

196 ms

pluggables.css

pluggables.css

13 ms

webs_common.js

webs_common.js

16 ms

websover.min.js

websover.min.js

15 ms

templatebase.css

templatebase.css

17 ms

.design.css

.design.css

84 ms

fw.js

fw.js

29 ms

fwml.css

fwml.css

4 ms

buttons.css

buttons.css

3 ms

widget.php

widget.php

20 ms

fwSiteSubscribe_sidebar.js

fwSiteSubscribe_sidebar.js

47 ms

collector.js

collector.js

3 ms

escort.js

escort.js

4 ms

style.css

style.css

5 ms

bg-body.jpg

bg-body.jpg

115 ms

invisible_big.JPG

invisible_big.JPG

130 ms

ga.js

ga.js

35 ms

button1-share.gif

button1-share.gif

11 ms

core201.js

core201.js

28 ms

hit.asp

hit.asp

123 ms

facebook_share_icon.gif

facebook_share_icon.gif

110 ms

bg.png

bg.png

76 ms

bg-head.gif

bg-head.gif

78 ms

nav-top.gif

nav-top.gif

75 ms

nav-bottom.gif

nav-bottom.gif

78 ms

bg-h2.gif

bg-h2.gif

76 ms

user.png

user.png

22 ms

3bac_35.jpg

3bac_35.jpg

115 ms

fwSiteSubscribe.css

fwSiteSubscribe.css

58 ms

__utm.gif

__utm.gif

43 ms

widget020.top.svg.css

widget020.top.svg.css

33 ms

menu174.js

menu174.js

22 ms

.i

.i

55 ms

44ab16746a0e83305b3f6b334417f8c5.png

44ab16746a0e83305b3f6b334417f8c5.png

87 ms

41b9bd625707f7be678a79a90baf1c17.JPG

41b9bd625707f7be678a79a90baf1c17.JPG

86 ms

sh200.html

sh200.html

18 ms

print.css

print.css

12 ms

hit.php

hit.php

60 ms

100lo.json

100lo.json

32 ms

3e1387b33e801afdbbd106febd480b45.jpg

3e1387b33e801afdbbd106febd480b45.jpg

64 ms

f4c149fdd9beb66a2b2059383fdc55ba.jpg

f4c149fdd9beb66a2b2059383fdc55ba.jpg

64 ms

aeff3fc86dece400068fc80db308ceea.jpg

aeff3fc86dece400068fc80db308ceea.jpg

63 ms

Accessibility Review

djinn.ca accessibility score

72

Accessibility Issues

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

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

Best Practices

djinn.ca best practices score

58

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

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

djinn.ca SEO score

71

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Djinn.ca 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 Djinn.ca main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

djinn.ca

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