4.5 sec in total
147 ms
3.7 sec
641 ms
Welcome to felcopruner.net homepage info - get ready to check Felco Pruner best content right away, or after learning these important things about felcopruner.net
The Felco Pruners web store offers it's customers a large selection of pruning, harvesting, and general gardening tools each of which cannot be matched elsewhere for quality or affordability. Fel...
Visit felcopruner.netWe analyzed Felcopruner.net page load time and found that the first response time was 147 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
felcopruner.net performance score
name
value
score
weighting
Value2.7 s
58/100
10%
Value6.3 s
10/100
25%
Value4.1 s
79/100
10%
Value300 ms
79/100
30%
Value0
100/100
15%
Value14.1 s
10/100
10%
147 ms
29 ms
96 ms
61 ms
128 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Felcopruner.net, 2% (3 requests) were made to Seal.alphassl.com and 1% (1 request) were made to Staticw2.yotpo.com. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Seal.alphassl.com.
Page size can be reduced by 564.5 kB (50%)
1.1 MB
570.7 kB
In fact, the total size of Felcopruner.net main page is 1.1 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. 70% of websites need less resources to load. Images take 504.9 kB which makes up the majority of the site volume.
Potential reduce by 102.2 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 24.4 kB, which is 21% 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 102.2 kB or 90% of the original size.
Potential reduce by 256.6 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, Felco Pruner needs image optimization as it can save up to 256.6 kB or 51% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 205.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 205.3 kB or 45% of the original size.
Potential reduce by 361 B
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. Felcopruner.net has all CSS files already compressed.
Number of requests can be reduced by 108 (84%)
128
20
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Felco Pruner. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 106 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.theprunerwarehouse.com
147 ms
calendar.css
29 ms
styles-m.css
96 ms
styles-l.css
61 ms
require.js
128 ms
mixins.js
70 ms
requirejs-config.js
65 ms
polyfill.js
67 ms
alpha_image_115-55_en.js
23 ms
widget.js
125 ms
alpha_noscript_115-55_en.gif
211 ms
siteSeal.do
3269 ms
pruners_WORKING_3b.png
337 ms
Slider_Felco_2_1.jpg
149 ms
bahco_bcl20ib_cordless_battery_powered_pruner.jpg
201 ms
sca3_4.jpg
211 ms
zenport_ep108_cordless_pruner.jpg
221 ms
felco_21_2.jpg
241 ms
bahco_px-m2.png
291 ms
ep2.jpg
290 ms
felco_2_1_1.jpg
333 ms
felco_921_holster.jpg
333 ms
silky_ultra_accel_240mm.jpg
386 ms
felco_6_sale.jpg
382 ms
jquery.mobile.custom.js
96 ms
dataPost.js
98 ms
bootstrap.js
95 ms
jquery.js
114 ms
translate-inline.js
93 ms
responsive.js
102 ms
theme.js
101 ms
translate.js
101 ms
opensans-400.woff
134 ms
opensans-300.woff
156 ms
opensans-600.woff
132 ms
opensans-700.woff
132 ms
domReady.js
153 ms
jquery.cookie.js
152 ms
Luma-Icons.woff
74 ms
main.js
72 ms
bootstrap.js
70 ms
template.js
90 ms
dialog.js
100 ms
confirm.js
95 ms
widget.js
96 ms
jquery.js
93 ms
smart-keyboard-handler.js
91 ms
mage.js
104 ms
ie-class-fixer.js
116 ms
tabs.js
113 ms
common.js
95 ms
jquery-migrate.js
96 ms
matchMedia.js
96 ms
knockout.js
96 ms
knockout-es5.js
66 ms
underscore.js
68 ms
engine.js
86 ms
bootstrap.js
64 ms
observable_array.js
61 ms
bound-nodes.js
123 ms
scripts.js
119 ms
modal.js
118 ms
jquery.storageapi.min.js
117 ms
button.js
115 ms
draggable.js
118 ms
position.js
118 ms
resizable.js
121 ms
core.js
106 ms
collapsible.js
150 ms
knockout-repeat.js
105 ms
knockout-fast-foreach.js
108 ms
renderer.js
92 ms
resizable.js
90 ms
i18n.js
91 ms
scope.js
92 ms
range.js
91 ms
mage-init.js
108 ms
keyboard.js
108 ms
optgroup.js
108 ms
after-render.js
108 ms
autoselect.js
108 ms
datepicker.js
110 ms
outer_click.js
116 ms
fadeVisible.js
117 ms
collapsible.js
116 ms
staticChecked.js
117 ms
simple-checked.js
117 ms
bind-html.js
122 ms
tooltip.js
134 ms
color-picker.js
133 ms
observable_source.js
107 ms
console-logger.js
107 ms
wrapper.js
106 ms
events.js
107 ms
es6-collections.js
127 ms
text.js
122 ms
key-codes.js
125 ms
mouse.js
119 ms
async.js
103 ms
registry.js
103 ms
slider.js
100 ms
loader.js
92 ms
main.js
119 ms
calendar.js
118 ms
moment.js
124 ms
spectrum.js
106 ms
tinycolor.js
107 ms
class.js
104 ms
local.js
133 ms
logger.js
130 ms
entry-factory.js
143 ms
console-output-handler.js
130 ms
formatter.js
142 ms
message-pool.js
143 ms
levels-pool.js
144 ms
logger-utils.js
142 ms
modal-popup.html
124 ms
modal-slide.html
145 ms
modal-custom.html
148 ms
js-translation.json
146 ms
tooltip.html
153 ms
dom-observer.js
86 ms
bindings.js
87 ms
datepicker.js
86 ms
timepicker.js
87 ms
arrays.js
52 ms
compare.js
52 ms
misc.js
51 ms
objects.js
53 ms
strings.js
54 ms
template.js
51 ms
entry.js
36 ms
MutationObserver.js
37 ms
FormData.js
30 ms
print.css
29 ms
felcopruner.net 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.
felcopruner.net 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
felcopruner.net SEO score
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Felcopruner.net 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 Felcopruner.net 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.
felcopruner.net
Open Graph description is not detected on the main page of Felco Pruner. 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: