Tools & Wizards About Us
en.notfollow.me screenshot

Report Summary

  • 0

    Performance

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

en.notfollow.me

Page Load Speed

989 ms in total

First Response

17 ms

Resources Loaded

825 ms

Page Rendered

147 ms

en.notfollow.me screenshot

About Website

Welcome to en.notfollow.me homepage info - get ready to check En Notfollow best content for Argentina right away, or after learning these important things about en.notfollow.me

Find out who's not following you back on Twitter

Visit en.notfollow.me

Key Findings

We analyzed En.notfollow.me page load time and found that the first response time was 17 ms and then it took 972 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

en.notfollow.me performance score

0

Network Requests Diagram

en.notfollow.me

17 ms

en.notfollow.me

159 ms

style.87f06407.css

118 ms

asyncjs.php

98 ms

jquery.min.js

106 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original En.notfollow.me, 27% (12 requests) were made to Pbs.twimg.com and 22% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (200 ms) relates to the external source Platform.twitter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 20.9 kB (13%)

Content Size

159.6 kB

After Optimization

138.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of En.notfollow.me main page is 159.6 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. 40% of websites need less resources to load. Images take 79.6 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 19.4 kB

  • Original 25.6 kB
  • After minification 23.3 kB
  • After compression 6.3 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 19.4 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 1.5 kB

  • Original 79.6 kB
  • After minification 78.1 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. En Notfollow images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

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

Requests Breakdown

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

Requests Now

42

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

en.notfollow.me

en.notfollow.me

17 ms

en.notfollow.me

en.notfollow.me

159 ms

style.87f06407.css

style.87f06407.css

118 ms

asyncjs.php

asyncjs.php

98 ms

jquery.min.js

jquery.min.js

106 ms

common.80266848.js

common.80266848.js

144 ms

home.a4011653.js

home.a4011653.js

113 ms

notfollowme.png

notfollowme.png

56 ms

sdk.js

sdk.js

111 ms

widgets.js

widgets.js

200 ms

analytics.js

analytics.js

174 ms

asyncspc.php

asyncspc.php

46 ms

JMT6VpzX_normal.jpg

JMT6VpzX_normal.jpg

118 ms

twe5hvq6_normal.jpg

twe5hvq6_normal.jpg

178 ms

jyzUuq1B_normal.jpg

jyzUuq1B_normal.jpg

131 ms

xXwm-rUJ_normal.jpg

xXwm-rUJ_normal.jpg

178 ms

vOT2nyRS_normal.jpg

vOT2nyRS_normal.jpg

109 ms

IezA5fc1_normal.jpeg

IezA5fc1_normal.jpeg

129 ms

sVNirE2N_normal.jpg

sVNirE2N_normal.jpg

130 ms

TCJQzdzC_normal.jpg

TCJQzdzC_normal.jpg

130 ms

r7kayY7d_normal.jpg

r7kayY7d_normal.jpg

152 ms

c44Pr-yH_normal.jpg

c44Pr-yH_normal.jpg

152 ms

Fk-v1AaG_normal.jpg

Fk-v1AaG_normal.jpg

188 ms

BNHwsFFG_normal.jpg

BNHwsFFG_normal.jpg

151 ms

lg.php

lg.php

59 ms

105 ms

xd_arbiter.php

xd_arbiter.php

85 ms

collect

collect

38 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

30 ms

collect

collect

51 ms

follow_button.6a78875565a912489e9aef879c881358.en.html

follow_button.6a78875565a912489e9aef879c881358.en.html

46 ms

page.php

page.php

61 ms

info.json

info.json

169 ms

q8sTdrz2ueE.css

q8sTdrz2ueE.css

28 ms

_rx8naC75Dy.js

_rx8naC75Dy.js

36 ms

t-KLv3gqZy0.js

t-KLv3gqZy0.js

53 ms

uLtKx7ldlvR.js

uLtKx7ldlvR.js

56 ms

10392314_900848589927824_2763465298456639361_n.png

10392314_900848589927824_2763465298456639361_n.png

53 ms

10530925_841839539162063_6020191443987968792_n.png

10530925_841839539162063_6020191443987968792_n.png

14 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

10 ms

CSXXCvknpgK.png

CSXXCvknpgK.png

10 ms

R9a_DtVRZgv.js

R9a_DtVRZgv.js

3 ms

cUDgRFxaoIk.js

cUDgRFxaoIk.js

4 ms

0JBr1QHp8Gi.js

0JBr1QHp8Gi.js

5 ms

kDOzhTr2W91.js

kDOzhTr2W91.js

5 ms

Accessibility Review

en.notfollow.me accessibility score

53

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

Document doesn't have a <title> element

High

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

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

en.notfollow.me best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

en.notfollow.me SEO score

83

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

Document doesn't have a <title> element

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise En.notfollow.me can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that En.notfollow.me 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

en.notfollow.me

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