4 sec in total
972 ms
2.7 sec
344 ms
Click here to check amazing Share content for Canada. Otherwise, check out these important facts you probably never knew about share.cat
share.cat is your first and best source for information about share. Here you will also find topics relating to issues of general interest. We hope you find what you are looking for!
Visit share.catWe analyzed Share.cat page load time and found that the first response time was 972 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
share.cat performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value5.2 s
23/100
25%
Value8.1 s
21/100
10%
Value2,720 ms
3/100
30%
Value0
100/100
15%
Value22.0 s
1/100
10%
972 ms
337 ms
34 ms
514 ms
254 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 16% of them (19 requests) were addressed to the original Share.cat, 8% (10 requests) were made to Static.xx.fbcdn.net and 8% (10 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Content-feed.com.
Page size can be reduced by 698.8 kB (41%)
1.7 MB
997.5 kB
In fact, the total size of Share.cat main page is 1.7 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 616.4 kB which makes up the majority of the site volume.
Potential reduce by 68.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 68.5 kB or 76% of the original size.
Potential reduce by 5.9 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. Share images are well optimized though.
Potential reduce by 306.2 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 306.2 kB or 50% of the original size.
Potential reduce by 318.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. Share.cat needs all CSS files to be minified and compressed as it can save up to 318.1 kB or 85% of the original size.
Number of requests can be reduced by 66 (61%)
109
43
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Share. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
share.cat
972 ms
main.min.css
337 ms
bootstrap.min.css
34 ms
style.min.css
514 ms
font-awesome.min.css
254 ms
jquery.min.js
63 ms
adsbygoogle.js
5 ms
Modernizr.min.js
166 ms
dialogFx.js
169 ms
popup_maker.js
182 ms
flat-ui.min.js
495 ms
jquery.validate.min.js
187 ms
jquery.validate.laravalid.js
181 ms
sdk.js
27 ms
atrk.js
82 ms
analytics.min.js
392 ms
piwik.js
265 ms
fbevents.js
24 ms
analytics.js
27 ms
gc1.jpg
1124 ms
resolve.jpg
819 ms
pb2-3.jpg
851 ms
pb5-1.jpg
1199 ms
cb1-1.jpg
1123 ms
ma1.jpeg
1283 ms
dash_logo.png
112 ms
cb4.jpg
166 ms
Wedding.jpg
288 ms
lato-regular.woff
284 ms
lato-light.woff
287 ms
lato-bold.woff
239 ms
lato-black.woff
240 ms
fontawesome-webfont.woff
286 ms
256 ms
ca-pub-8367835315857705.js
60 ms
zrt_lookup.html
201 ms
show_ads_impl.js
109 ms
301 ms
atrk.gif
214 ms
xd_arbiter.php
74 ms
xd_arbiter.php
194 ms
collect
265 ms
show_ads.js
193 ms
test.png
367 ms
ads
304 ms
osd.js
88 ms
ads
284 ms
ads-sync.js
51 ms
no-impression.gif
28 ms
flat-ui-icons-regular.woff
139 ms
p
345 ms
m_js_controller.js
112 ms
abg.js
179 ms
googlelogo_color_112x36dp.png
106 ms
15192684685596781766
218 ms
mixpanel-2-latest.min.js
174 ms
roundtrip.js
171 ms
atrk.js
52 ms
js
170 ms
inspectlet.js
71 ms
w.js
169 ms
prum.min.js
124 ms
137 ms
collect
12 ms
favicon
214 ms
nessie_icon_tiamat_white.png
103 ms
703678882
154 ms
s
107 ms
x_button_blue2.png
73 ms
clickstream.min.js
76 ms
47 ms
page.php
154 ms
7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js
22 ms
storage.luckyorange.net
53 ms
667JF5HVQZANBOS6N32GMG.js
239 ms
in.php
229 ms
settings.luckyorange.net
30 ms
TWq8MvTxuc6.css
37 ms
_rx8naC75Dy.js
41 ms
3o1espZ6Mhb.js
55 ms
nfTYZZc0iSn.js
58 ms
20 ms
mutation.min.js
48 ms
reset.css
10 ms
11824975_861576040594952_2615565132913539308_n.png
121 ms
11232946_846292932123263_5601559317360744660_n.png
85 ms
12651160_1043243039071949_8142943731665050226_n.jpg
85 ms
10491282_1524169451243496_3822367880847307990_n.jpg
85 ms
12208630_472557752924617_1104756308328218963_n.jpg
85 ms
10678626_892652097412271_6782491240166061941_n.jpg
85 ms
12541162_471315309735310_3105647220524590908_n.jpg
85 ms
12745426_963476467053935_7388118942112111419_n.jpg
89 ms
10399232_575280482627984_3873412252798941899_n.jpg
89 ms
12743855_167303903649107_4447415920568011873_n.jpg
93 ms
wL6VQj7Ab77.png
58 ms
s7jcwEQH7Sx.png
64 ms
out
23 ms
tr
45 ms
41 ms
out
15 ms
out
15 ms
out
18 ms
out
23 ms
out
24 ms
out
23 ms
out
22 ms
u.php
62 ms
sync
23 ms
adsct
87 ms
pixel
47 ms
24 ms
R9a_DtVRZgv.js
8 ms
cUDgRFxaoIk.js
9 ms
0JBr1QHp8Gi.js
9 ms
kDOzhTr2W91.js
14 ms
sd
12 ms
377928.gif
13 ms
in
4 ms
nr-768.min.js
16 ms
ui
34 ms
aa40d22e86
52 ms
beacon.gif
93 ms
share.cat 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
Links do not have a discernible name
share.cat 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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
share.cat 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Share.cat 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 Share.cat 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.
share.cat
Open Graph data is detected on the main page of Share. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: