17.5 sec in total
5 sec
12.2 sec
272 ms
Visit flytraps.com now to see the best up-to-date Flytraps content and also check out these interesting facts you probably never knew about flytraps.com
Visit flytraps.comWe analyzed Flytraps.com page load time and found that the first response time was 5 sec and then it took 12.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
flytraps.com performance score
name
value
score
weighting
Value16.7 s
0/100
10%
Value17.4 s
0/100
25%
Value33.8 s
0/100
10%
Value740 ms
40/100
30%
Value0.273
45/100
15%
Value20.6 s
2/100
10%
5003 ms
52 ms
166 ms
203 ms
172 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 84% of them (80 requests) were addressed to the original Flytraps.com, 8% (8 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (5 sec) belongs to the original domain Flytraps.com.
Page size can be reduced by 245.2 kB (32%)
766.0 kB
520.8 kB
In fact, the total size of Flytraps.com main page is 766.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. 65% of websites need less resources to load. Javascripts take 308.7 kB which makes up the majority of the site volume.
Potential reduce by 84.5 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 84.5 kB or 82% of the original size.
Potential reduce by 0 B
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. Flytraps images are well optimized though.
Potential reduce by 64.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 64.7 kB or 21% of the original size.
Potential reduce by 96.0 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. Flytraps.com needs all CSS files to be minified and compressed as it can save up to 96.0 kB or 32% of the original size.
Number of requests can be reduced by 78 (93%)
84
6
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flytraps. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 34 to 1 for CSS and as a result speed up the page load time.
flytraps.com
5003 ms
js
52 ms
blocks-checkout.css
166 ms
style.min.css
203 ms
common-style.css
172 ms
style-index.css
172 ms
blocks.style.build.css
181 ms
woocommerce-layout.css
176 ms
woocommerce.css
194 ms
font-awesome.min.css
198 ms
simple-line-icons.css
199 ms
htflexboxgrid.css
205 ms
slick.css
206 ms
woolentor-widgets.css
249 ms
yith-quick-view.css
216 ms
style.css
214 ms
bootstrap.min.css
234 ms
style-main.min.css
230 ms
blocks-frontend.min.css
232 ms
line-awesome.min.css
243 ms
jquery.mCustomScrollbar.min.css
240 ms
animate.min.css
260 ms
css
35 ms
css2
72 ms
woocommerce-style.min.css
256 ms
elementor-icons.min.css
261 ms
frontend.min.css
270 ms
swiper.min.css
263 ms
post-15.css
275 ms
frontend.min.css
324 ms
global.css
283 ms
post-877.css
280 ms
css
71 ms
wp-polyfill-inert.min.js
285 ms
regenerator-runtime.min.js
291 ms
wp-polyfill.min.js
308 ms
hooks.min.js
304 ms
w.js
17 ms
frontend-gtag.min.js
308 ms
jquery.min.js
316 ms
jquery-migrate.min.js
317 ms
jquery.blockUI.min.js
435 ms
photoswipe.min.css
278 ms
default-skin.min.css
273 ms
add-to-cart.min.js
271 ms
js.cookie.min.js
267 ms
woocommerce.min.js
262 ms
script.js
248 ms
sourcebuster.min.js
244 ms
order-attribution.min.js
244 ms
slick.min.js
241 ms
accordion.min.js
239 ms
frontend.min.js
269 ms
bootstrap.min.js
259 ms
jquery.easing.1.3.min.js
259 ms
modernizr.min.js
242 ms
ResizeSensor.min.js
241 ms
theia-sticky-sidebar.min.js
233 ms
jquery.mCustomScrollbar.min.js
323 ms
main.min.js
318 ms
smush-lazy-load.min.js
311 ms
cart-fragments.min.js
306 ms
underscore.min.js
302 ms
wp-util.min.js
302 ms
add-to-cart-variation.min.js
301 ms
jquery.zoom.min.js
289 ms
photoswipe.min.js
290 ms
photoswipe-ui-default.min.js
284 ms
single-product.min.js
279 ms
webpack-pro.runtime.min.js
279 ms
webpack.runtime.min.js
311 ms
frontend-modules.min.js
298 ms
i18n.min.js
294 ms
frontend.min.js
294 ms
waypoints.min.js
286 ms
core.min.js
283 ms
g.gif
110 ms
frontend.min.js
203 ms
elements-handlers.min.js
203 ms
frontend.min.js
203 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQXMFrLgTteV4.ttf
124 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_GbQXMFrLgTteV4.ttf
160 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_ObXXMFrLgTteV4.ttf
198 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_N_XXMFrLgTteV4.ttf
199 ms
la-solid-900.woff
285 ms
la-regular-400.woff
266 ms
pxiEyp8kv8JHgFVrJJfed3FHGPc.ttf
172 ms
pxiByp8kv8JHgFVrLGT9Z1xlEN2JQEk.ttf
172 ms
pxiByp8kv8JHgFVrLDz8Z1xlEN2JQEk.ttf
172 ms
pxiByp8kv8JHgFVrLCz7Z1xlEN2JQEk.ttf
172 ms
jquery.mousewheel.min.js
119 ms
cropped-cropped-wplanty01-1.gif
42 ms
wally-300x300.jpg
110 ms
woocommerce-smallscreen.css
25 ms
size-chart-300x300.jpg
27 ms
flytraps.com accessibility score
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
flytraps.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
flytraps.com SEO score
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 Flytraps.com 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 Flytraps.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.
flytraps.com
Open Graph description is not detected on the main page of Flytraps. 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: