1.2 sec in total
337 ms
762 ms
100 ms
Visit nil.pe now to see the best up-to-date Nil content and also check out these interesting facts you probably never knew about nil.pe
Soluciones integrales para la industria metalmecánica en Lima y todo el Perú.
Visit nil.peWe analyzed Nil.pe page load time and found that the first response time was 337 ms and then it took 862 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
nil.pe performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value5.1 s
25/100
25%
Value4.2 s
78/100
10%
Value50 ms
100/100
30%
Value0.177
68/100
15%
Value4.6 s
82/100
10%
337 ms
26 ms
31 ms
29 ms
30 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 84% of them (53 requests) were addressed to the original Nil.pe, 10% (6 requests) were made to Fonts.gstatic.com and 6% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (337 ms) belongs to the original domain Nil.pe.
Page size can be reduced by 259.9 kB (49%)
531.0 kB
271.1 kB
In fact, the total size of Nil.pe main page is 531.0 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. 35% of websites need less resources to load. Images take 251.0 kB which makes up the majority of the site volume.
Potential reduce by 18.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. This page needs HTML code to be minified as it can gain 4.0 kB, which is 17% 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 18.4 kB or 79% of the original size.
Potential reduce by 40.5 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, Nil needs image optimization as it can save up to 40.5 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 124.7 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 124.7 kB or 76% of the original size.
Potential reduce by 76.3 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. Nil.pe needs all CSS files to be minified and compressed as it can save up to 76.3 kB or 82% of the original size.
Number of requests can be reduced by 43 (77%)
56
13
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nil. 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 29 to 1 for CSS and as a result speed up the page load time.
nil.pe
337 ms
system.base.css
26 ms
system.menus.css
31 ms
system.messages.css
29 ms
system.theme.css
30 ms
comment.css
31 ms
field.css
30 ms
mollom.css
39 ms
node.css
44 ms
search.css
44 ms
user.css
44 ms
views.css
45 ms
ctools.css
45 ms
superfish.css
53 ms
960.css
60 ms
720.css
57 ms
mobile.css
58 ms
column-layouts.css
60 ms
flexslider.css
59 ms
style.css
79 ms
style-orange.css
70 ms
sourcesanspro-font.css
72 ms
titilliumweb-font.css
73 ms
exo-font.css
74 ms
ptserif-font.css
74 ms
local.css
85 ms
jquery.js
113 ms
jquery-extend-3.4.0.js
89 ms
jquery-html-prefilter-3.5.0-backport.js
89 ms
jquery.once.js
89 ms
drupal.js
93 ms
jquery.mobilemenu.js
101 ms
supposition.js
103 ms
superfish.js
103 ms
supersubs.js
104 ms
superfish.js
107 ms
jquery.flexslider.js
124 ms
css
20 ms
css
37 ms
css
39 ms
css
37 ms
backtotop-arrow.png
18 ms
company-home.png
16 ms
company-phone.png
18 ms
company-email.png
18 ms
search-button.png
19 ms
nil_0.png
55 ms
main-menu-arrow-black.png
30 ms
main-menu-arrow-white.png
31 ms
dormer_pramet_s.jpg
60 ms
abrasivos_s.jpg
47 ms
facebook.png
32 ms
twitter.png
45 ms
googleplus.png
46 ms
youtube.png
46 ms
more-arrow.png
59 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qO67g.ttf
32 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlBdr.ttf
109 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlBdr.ttf
64 ms
direction.png
15 ms
NaPecZTIAOhVxoMyOr9n_E7fdM3mCA.ttf
4 ms
NaPDcZTIAOhVxoMyOr9n_E7ffHjDGIVzZg.ttf
6 ms
NaPDcZTIAOhVxoMyOr9n_E7ffEDBGIVzZg.ttf
129 ms
nil.pe 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.
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
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
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
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.
nil.pe best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
nil.pe 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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nil.pe 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 Nil.pe 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.
nil.pe
Open Graph description is not detected on the main page of Nil. 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: