17.9 sec in total
5.3 sec
12.2 sec
412 ms
Welcome to inkd.us homepage info - get ready to check Inkd best content right away, or after learning these important things about inkd.us
View, share and rate tattoos
Visit inkd.usWe analyzed Inkd.us page load time and found that the first response time was 5.3 sec and then it took 12.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
inkd.us performance score
name
value
score
weighting
Value2.0 s
85/100
10%
Value4.3 s
41/100
25%
Value2.0 s
99/100
10%
Value40 ms
100/100
30%
Value0
100/100
15%
Value3.0 s
96/100
10%
5268 ms
222 ms
168 ms
194 ms
164 ms
Our browser made a total of 148 requests to load all elements on the main page. We found that 39% of them (57 requests) were addressed to the original Inkd.us, 17% (25 requests) were made to Static.xx.fbcdn.net and 7% (10 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (5.3 sec) belongs to the original domain Inkd.us.
Page size can be reduced by 584.4 kB (44%)
1.3 MB
752.7 kB
In fact, the total size of Inkd.us main page is 1.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 601.9 kB which makes up the majority of the site volume.
Potential reduce by 63.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. 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 63.2 kB or 79% of the original size.
Potential reduce by 20.1 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. Inkd images are well optimized though.
Potential reduce by 365.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 365.4 kB or 61% of the original size.
Potential reduce by 135.6 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. Inkd.us needs all CSS files to be minified and compressed as it can save up to 135.6 kB or 85% of the original size.
Number of requests can be reduced by 79 (57%)
139
60
The browser has sent 139 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Inkd. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 57 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
inkd.us
5268 ms
wp-emoji-release.min.js
222 ms
PicsMash.css
168 ms
gdsr.css.php
194 ms
rating.css
164 ms
css
32 ms
dcwss.css
215 ms
lightbox.min.css
211 ms
unsemantic-grid.min.css
252 ms
style.css
293 ms
mobile.min.css
278 ms
font-awesome.min.css
312 ms
style.css
370 ms
jquery.js
481 ms
jquery-migrate.min.js
401 ms
myo-script.js
400 ms
gdsr.js
499 ms
jquery.social.stream.wall.1.2.js
504 ms
jquery.social.stream.1.4.3.min.js
517 ms
ai.js
518 ms
cgview.js
499 ms
jquery.colorbox-min.js
543 ms
easypaginate.min.js
564 ms
adsbygoogle.js
7 ms
show_ads.js
14 ms
api.js
45 ms
jquery.form.min.js
582 ms
wp-lightbox-2.min.js
610 ms
navigation.min.js
673 ms
dropdown.min.js
739 ms
navigation-search.min.js
735 ms
wp-embed.min.js
735 ms
PinExt.png
25 ms
dreamhost-logo-88x31.png
63 ms
sexy-tattoo58.jpg
360 ms
evil-tattoo3.jpg
448 ms
timthumb.php
854 ms
timthumb.php
734 ms
timthumb.php
900 ms
timthumb.php
899 ms
timthumb.php
818 ms
timthumb.php
897 ms
timthumb.php
895 ms
timthumb.php
914 ms
timthumb.php
921 ms
timthumb.php
1461 ms
timthumb.php
1077 ms
timthumb.php
1037 ms
timthumb.php
956 ms
timthumb.php
1483 ms
timthumb.php
1105 ms
timthumb.php
1207 ms
timthumb.php
1372 ms
timthumb.php
1496 ms
rss.png
1272 ms
sexy-tattoo43.jpg
1495 ms
sexy-tattoo105.jpg
1393 ms
evil-tattoo2.jpg
1511 ms
powered_by_envato_api-88x31.png
57 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
59 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
91 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
264 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
286 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
286 ms
fontawesome-webfont.woff
1529 ms
ca-pub-7601753146294661.js
279 ms
zrt_lookup.html
285 ms
show_ads_impl.js
76 ms
all.js
458 ms
widgets.js
349 ms
plusone.js
349 ms
ad.ezp
1608 ms
cm
263 ms
stars12.png
1618 ms
ads
404 ms
recaptcha__en.js
189 ms
osd.js
167 ms
border1.png
1397 ms
border2.png
1408 ms
loading.gif
1407 ms
ads
300 ms
show_ads_impl.js
71 ms
us_banner_hpc_88x31.gif
123 ms
34 ms
General_Logo_88x31.jpg
14 ms
ads
219 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
70 ms
cb=gapi.loaded_0
56 ms
cb=gapi.loaded_1
78 ms
fastbutton
327 ms
fastbutton
172 ms
220 ms
xd_arbiter.php
283 ms
xd_arbiter.php
568 ms
15969958180415185898
92 ms
abg.js
65 ms
m_js_controller.js
85 ms
googlelogo_color_112x36dp.png
32 ms
postmessageRelay
226 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
121 ms
css
223 ms
x_button_blue2.png
77 ms
s
75 ms
rs=AGLTcCPp65oTnX7XI_ISus95mcUHkH7hXw
76 ms
cb=gapi.loaded_0
82 ms
cb=gapi.loaded_1
78 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
86 ms
3193398744-postmessagerelay.js
129 ms
rpc:shindig_random.js
137 ms
nessie_icon_tiamat_white.png
79 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
66 ms
cb=gapi.loaded_0
5 ms
jot.html
29 ms
activeview
13 ms
Hobo-Fresh-Beard-Kit-Ad-160[1].jpg
6 ms
widgets.js
33 ms
ping
44 ms
comments.php
2314 ms
comments.php
2228 ms
ui
15 ms
like.php
167 ms
like.php
175 ms
qeKvIRsJabD.js
549 ms
LVx-xkvaJ0b.png
613 ms
qeKvIRsJabD.js
764 ms
kyEKgjk51ZE.css
70 ms
xgj7bXhJNEH.css
72 ms
yBwS6rJyogl.css
138 ms
ZeuPykSxSED.css
204 ms
q68gy-v_YMF.js
271 ms
FJmpeSpHpjS.js
335 ms
0wM5s1Khldu.js
235 ms
LTv6ZK-5zxz.js
474 ms
1FCa-btixu2.js
235 ms
Oagsvfb4VWi.js
358 ms
FyxLoiww5bU.js
357 ms
HaMjR2eXz4B.js
302 ms
WN2wSsLOuKy.js
357 ms
HgJbVwzBr8E.js
357 ms
Q4A0UyjU8W2.js
401 ms
1bNoFZUdlYZ.js
408 ms
odA9sNLrE86.jpg
75 ms
fav.png
72 ms
OZFAYTv-ZUg.js
70 ms
I6-MnjEovm5.js
69 ms
pQrUxxo5oQp.js
102 ms
wL6VQj7Ab77.png
100 ms
K00K-UgnsKu.png
101 ms
inkd.us 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
button, link, and menuitem elements do not have accessible names.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
inkd.us best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
inkd.us 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
Image elements do not have [alt] attributes
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 Inkd.us 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 Inkd.us 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.
inkd.us
Open Graph data is detected on the main page of Inkd. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: