10.6 sec in total
2.8 sec
7 sec
851 ms
Click here to check amazing Nellooli content. Otherwise, check out these important facts you probably never knew about nellooli.com
Visit nellooli.comWe analyzed Nellooli.com page load time and found that the first response time was 2.8 sec and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
nellooli.com performance score
name
value
score
weighting
Value1.3 s
98/100
10%
Value3.4 s
67/100
25%
Value2.7 s
96/100
10%
Value540 ms
55/100
30%
Value0
100/100
15%
Value3.6 s
91/100
10%
2800 ms
66 ms
110 ms
216 ms
195 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 66% of them (67 requests) were addressed to the original Nellooli.com, 20% (20 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Nellooli.com.
Page size can be reduced by 2.2 MB (45%)
5.0 MB
2.7 MB
In fact, the total size of Nellooli.com main page is 5.0 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 101.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 101.4 kB or 86% of the original size.
Potential reduce by 855.3 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. Obviously, Nellooli needs image optimization as it can save up to 855.3 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 597.3 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 597.3 kB or 70% of the original size.
Potential reduce by 695.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. Nellooli.com needs all CSS files to be minified and compressed as it can save up to 695.7 kB or 84% of the original size.
Number of requests can be reduced by 52 (65%)
80
28
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nellooli. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
www.nellooli.com
2800 ms
webfont.js
66 ms
styles.css
110 ms
bootstrap.min.css
216 ms
font-awesome.min.css
195 ms
outline.min.css
1148 ms
hgr-vc-extender-elements.min.css
227 ms
settings.css
250 ms
css
51 ms
css
69 ms
css
87 ms
settings.css
347 ms
bootstrap.min.css
349 ms
icons.css
287 ms
font-awesome.min.css
296 ms
component.css
390 ms
venobox.css
388 ms
style.css
504 ms
js_composer.css
525 ms
jquery.js
770 ms
jquery-migrate.min.js
706 ms
bootstrap.min.js
568 ms
jquery.themepunch.tools.min.js
738 ms
jquery.themepunch.revolution.min.js
737 ms
jquery.themepunch.essential.min.js
930 ms
modernizr.custom.js
789 ms
js
85 ms
css
21 ms
style.css
84 ms
comment-reply.min.js
93 ms
jquery.form.min.js
173 ms
scripts.js
183 ms
bootstrap.min.js
144 ms
imagesloaded.js
148 ms
isotope.pkgd.min.js
213 ms
waypoints.min.js
223 ms
venobox.min.js
227 ms
app.js
260 ms
js_composer_front.js
284 ms
script-ck.js
309 ms
jquery.scrolly-ck.js
286 ms
jquery.appear.js
292 ms
countto.js
339 ms
bg-video-ck.js
353 ms
jquery.hoverdir.js
361 ms
hgr-advimage.js
346 ms
tooltip.js
364 ms
hgrblogposts.js
401 ms
logo.png
109 ms
11354529633_fa55d9ed0d_o.jpg
463 ms
449533818_9dd134426e_o1.jpg
784 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
30 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
30 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
31 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
30 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
31 ms
b9QBgL0iMZfDSpmcXcE8nL3QFSXBldIn45k5A7iXhnc.ttf
30 ms
Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf
31 ms
b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf
31 ms
toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf
31 ms
arrow1.svg
364 ms
logo1.png
364 ms
NDS-e1415345244706.jpg
364 ms
dummy-portfolio-3.jpg
364 ms
KM-150x150.png
462 ms
NPR-150x150.png
462 ms
KumardasSir-e1419400069625-150x150.jpg
459 ms
klear.jpg
459 ms
NDS111.jpg
476 ms
dome.jpg
475 ms
Skanray1.jpg
466 ms
open-white-box.jpg
1447 ms
fontawesome-webfont.woff
547 ms
fontawesome-webfont.woff
494 ms
outline.woff
505 ms
outline.woff
660 ms
git-parallax3.jpg
688 ms
git-parallax2.jpg
787 ms
iframe_api
257 ms
bullet.png
432 ms
large_left.png
432 ms
large_right.png
472 ms
ajax-loader.gif
505 ms
JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf
16 ms
1ImRNPx4870-D9a1EBUdPC3USBnSvpkopQaUR-2r7iU.ttf
66 ms
PKCRbVvRfd5n7BTjtGiFZC3USBnSvpkopQaUR-2r7iU.ttf
66 ms
xkvoNo9fC8O2RDydKj12by3USBnSvpkopQaUR-2r7iU.ttf
66 ms
CcKI4k9un7TZVWzRVT-T8y3USBnSvpkopQaUR-2r7iU.ttf
66 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
65 ms
-_Ctzj9b56b8RgXW8FAriS3USBnSvpkopQaUR-2r7iU.ttf
66 ms
8KhZd3VQBtXTAznvKjw-ky3USBnSvpkopQaUR-2r7iU.ttf
67 ms
RJMlAoFXXQEzZoMSUteGWKCWcynf_cDxXwCLxiixG1c.ttf
66 ms
www-widgetapi.js
19 ms
f4Q55qJ9TJM
86 ms
www-embed-player-vfl-z2BtK.css
36 ms
www-embed-player.js
73 ms
base.js
106 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
89 ms
ad_status.js
92 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
130 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
131 ms
nellooli.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
nellooli.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
nellooli.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nellooli.com 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 Nellooli.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.
nellooli.com
Open Graph description is not detected on the main page of Nellooli. 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: