5.2 sec in total
398 ms
4.3 sec
426 ms
Visit funzing.com now to see the best up-to-date Funzing content for Israel and also check out these interesting facts you probably never knew about funzing.com
A community marketplace to discover and share the best local experiences, activities and things to do in your city or create your own
Visit funzing.comWe analyzed Funzing.com page load time and found that the first response time was 398 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
funzing.com performance score
name
value
score
weighting
Value6.8 s
2/100
10%
Value23.3 s
0/100
25%
Value21.3 s
0/100
10%
Value8,230 ms
0/100
30%
Value0
100/100
15%
Value29.1 s
0/100
10%
398 ms
706 ms
21 ms
11 ms
19 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 15% of them (15 requests) were addressed to the original Funzing.com, 22% (21 requests) were made to D1cgjtrsdeqk19.cloudfront.net and 12% (12 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source D1cgjtrsdeqk19.cloudfront.net.
Page size can be reduced by 993.9 kB (31%)
3.2 MB
2.2 MB
In fact, the total size of Funzing.com main page is 3.2 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 1.9 MB which makes up the majority of the site volume.
Potential reduce by 164.8 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 164.8 kB or 82% of the original size.
Potential reduce by 23.7 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. Funzing images are well optimized though.
Potential reduce by 477.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 477.4 kB or 68% of the original size.
Potential reduce by 328.1 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. Funzing.com needs all CSS files to be minified and compressed as it can save up to 328.1 kB or 84% of the original size.
Number of requests can be reduced by 39 (44%)
88
49
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Funzing. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
funzing.com
398 ms
www.funzing.com
706 ms
application-ltr-10c2edd0bbad5c07b3a7b96d2687a9e8.css
21 ms
application-860247f7a71bc02e89a195b1821f355b.js
11 ms
funzing-db25d6415da56e19de2ae5be776b06f4.js
19 ms
ui-732984efa8bc52c1bf9c70229cd53785.js
19 ms
plugins-02d587fcbf48fb002e2b738f891cc0df.js
54 ms
funz-a3ae559021f491adb107cc1df525432b.js
52 ms
modules-9f4b97b7d36672352ea978498e824af7.js
52 ms
my-1d40c57dabf0633f82f034692da45cc4.js
54 ms
orders-cfc72695caa62af43525154a0911c802.js
53 ms
admin-4b1fdd0f441e8ceef28449837a27d919.js
54 ms
initializer-1999d21940ea011f9e09b8edcd8eadb7.js
54 ms
opensanshebrew.css
36 ms
heap-3361467110.js
183 ms
w.js
183 ms
gtm.js
216 ms
logo.png
199 ms
www-widgetapi.js
216 ms
js
208 ms
sdk.js
102 ms
fetch_modal_content
184 ms
1.jpg
875 ms
1.jpg
716 ms
11.jpg
741 ms
2.jpg
780 ms
10.jpg
1214 ms
blank.jpg
551 ms
3.jpg
1299 ms
4.jpg
1446 ms
5.jpg
1522 ms
6.jpg
1578 ms
7.jpg
1744 ms
8.jpg
2305 ms
9.jpg
2064 ms
sprite.png
1450 ms
ajax-loader.gif
1453 ms
step_1.jpg
1456 ms
step_2.jpg
1459 ms
step_3.jpg
1463 ms
OpenSansHebrew-Regular.woff
47 ms
OpenSansHebrew-Light.woff
68 ms
OpenSansHebrew-Bold.woff
105 ms
OpenSansHebrew-ExtraBold.woff
121 ms
fontawesome-webfont-1844e011f3379dd4187c4b0054d608ed.woff
45 ms
clickstream.min.js
52 ms
h
41 ms
analytics.js
57 ms
159 ms
storage.luckyorange.net
105 ms
xd_arbiter.php
52 ms
xd_arbiter.php
71 ms
newsletter_background.png
1314 ms
funzing_logo_small.png
1317 ms
collect
57 ms
settings.luckyorange.net
220 ms
ga-audiences
33 ms
15 ms
mutation.min.js
30 ms
reset.css
4 ms
nr-885.min.js
32 ms
u56s6162
76 ms
03fb71e304
62 ms
xd_arbiter.php
18 ms
intercom.bcfdf787.js
29 ms
ping
165 ms
echo.515e8809.js
8 ms
like_box.php
213 ms
Intercom_Profile.png
66 ms
icon-launcher-acquire.8a742481.png
15 ms
client-test
182 ms
client-test
187 ms
icon-preview-close.ec1a68fc.png
37 ms
11745736_10205976898815019_7916315039996799606_n.jpg
48 ms
julia_5.jpg
63 ms
lL2b34Z7dj7.css
41 ms
guHxiHaOfJH.css
54 ms
_rx8naC75Dy.js
60 ms
b94UUzHjapV.js
87 ms
0wM5s1Khldu.js
86 ms
TTCre3391I0.js
82 ms
11693892_1135154559831448_2326852029264200796_n.jpg
87 ms
10996024_1086524904694414_5872559696041882969_n.png
49 ms
1922281_10202193182328841_592040368_n.jpg
50 ms
11753691_105470456467929_6781635225029212539_n.jpg
52 ms
12734076_142426169478793_1699153346400471688_n.jpg
50 ms
11855625_951635481574919_842631633755625179_n.jpg
55 ms
1509646_10154027141259954_7477311969696339105_n.jpg
54 ms
12651069_10204002461262274_6486081142610627238_n.jpg
50 ms
12745778_107345709656321_8684904793892339800_n.jpg
53 ms
12141549_10207976501640105_4492475714955856234_n.jpg
52 ms
12802704_1002849739770454_689463507139948231_n.jpg
55 ms
12346369_979386345487048_7516222398589873138_n.jpg
54 ms
wL6VQj7Ab77.png
16 ms
s7jcwEQH7Sx.png
21 ms
I6-MnjEovm5.js
26 ms
f6T91Deal_q.js
26 ms
funzing.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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.
funzing.com 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
funzing.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Funzing.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Funzing.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.
funzing.com
Open Graph data is detected on the main page of Funzing. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: