5.7 sec in total
679 ms
3.8 sec
1.3 sec
Welcome to inktraveler.com homepage info - get ready to check Inktraveler best content right away, or after learning these important things about inktraveler.com
Japanese fountain pens stationery
Visit inktraveler.comWe analyzed Inktraveler.com page load time and found that the first response time was 679 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
inktraveler.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value18.5 s
0/100
25%
Value10.6 s
7/100
10%
Value760 ms
39/100
30%
Value1.234
1/100
15%
Value13.5 s
11/100
10%
679 ms
31 ms
208 ms
309 ms
312 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 94% of them (77 requests) were addressed to the original Inktraveler.com, 2% (2 requests) were made to Fonts.googleapis.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Inktraveler.com.
Page size can be reduced by 317.9 kB (11%)
2.8 MB
2.5 MB
In fact, the total size of Inktraveler.com main page is 2.8 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. 55% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 139.3 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 56.4 kB, which is 37% 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 139.3 kB or 91% of the original size.
Potential reduce by 23.0 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. Inktraveler images are well optimized though.
Potential reduce by 37.5 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 37.5 kB or 21% of the original size.
Potential reduce by 118.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. Inktraveler.com needs all CSS files to be minified and compressed as it can save up to 118.0 kB or 62% of the original size.
Number of requests can be reduced by 37 (48%)
77
40
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Inktraveler. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
679 ms
css
31 ms
theme.css
208 ms
font-awesome.min.css
309 ms
owl.carousel.css
312 ms
owl.theme.css
311 ms
owl.transitions.css
313 ms
front.css
314 ms
ps_socialfollow.css
314 ms
font-awesome.min.css
412 ms
bonslick_front.css
415 ms
slick.css
418 ms
slick-theme.css
417 ms
productcomments.css
415 ms
fixreviewlist17.css
418 ms
jquery.fancybox.css
517 ms
custom.css
617 ms
trackingClient.bundle.js
514 ms
js
52 ms
core.js
721 ms
theme.js
717 ms
front.js
523 ms
scrolltop.js
621 ms
bonslick_front.js
623 ms
slick.js
626 ms
jquery.fancybox.js
718 ms
jquery.scrollTo.js
719 ms
ps_shoppingcart.js
720 ms
parallax-background.js
730 ms
owl.carousel.js
820 ms
custom.js
821 ms
css
13 ms
base.css
211 ms
logo.svg
111 ms
icono-cesta.svg
168 ms
696ae983ab2ef169db120ab404a79d4e48a9e080_portada-IB.jpg
412 ms
8857c83af6b36b5e935bb85837a5066ef38af439_slide-02.jpg
508 ms
c8fccf926afcc8f9884196f6263a54c190ab781f_Naoshima%20kon%20slide%2000.jpg
410 ms
5ca637068001a582cf886997d379f40ead88c86b_slide-05.jpg
311 ms
b04445a406552803c5c9e96dfdfb228bcbb5c323_slide-06.jpg
515 ms
86f63b0db82c43dfeb632d0a5a0d4450131d1212_slide-07.jpg
417 ms
6bf06cd9c9b2a2b777c65499b6a748ca5b2b434b_Banner%20Portada%20inktraveler%20en.jpg
517 ms
Modulo%20categoria%20MD.jpg
619 ms
home-cuadernos-viajero.jpg
517 ms
home-estilograficas.jpg
624 ms
Modulo%20tintas%20shikiirori.jpg
614 ms
separator.png
619 ms
platinum-sterling-silver-pin-stripes.jpg
621 ms
pilot-capless-matte-black.jpg
624 ms
pilot-custom-maple-wood.jpg
718 ms
pilot-custom-742-signature-nib.jpg
721 ms
pilot-custom-742-falcon.jpg
721 ms
pilot-custom-743-black-coarse.jpg
725 ms
sailor-hocoro-dip-pen-replace-nib-f.jpg
729 ms
sailor-hocoro-dip-pen-replace-nib-fude.jpg
727 ms
sailor-hocoro-dip-pen-20mm.jpg
823 ms
sailor-hocoro-dip-pen-20mm.jpg
826 ms
sailor-hocoro-dip-pen-10mm.jpg
825 ms
sailor-hocoro-dip-pen-m.jpg
828 ms
kaweko-satsume-soseki.jpg
830 ms
stock-ohashido.jpg
832 ms
kaweko-murasaki-shikibu.jpg
927 ms
taccia-hiroshige-4-inks-set.jpg
930 ms
taccia-kakutate-asagi.jpg
928 ms
pilot-custom-823-smoke.jpg
931 ms
pilot-custom-urushi-vermillion.jpg
933 ms
823-wrench.jpg
936 ms
fondo-01.jpg
1032 ms
3935e107ea61866e60d7946dc6a962f1.svg
926 ms
49 ms
8b05d51ede908907d65695558974d86f.svg
873 ms
012cf6a10129e2275d79d6adac7f3b02.woff
878 ms
41 ms
ufonts.com_calvert-mt-bold.woff
763 ms
fontawesome-webfont.woff
665 ms
fontawesome-webfont.woff
736 ms
a67175d1ea11389d9107bd8c08f9d7d7.svg
724 ms
ffddcb3736980b23405b31142a324b62.svg
633 ms
afb2ed6d67613a724a420a39b4fe5b0d.svg
662 ms
b1db819132e64a3e01911a1413c33acf.svg
661 ms
0266b05265f317a7409560b751cd61e8.svg
662 ms
icono-contacto.svg
629 ms
inktraveler.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-hidden="true"] elements contain focusable descendents
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
inktraveler.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
inktraveler.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Inktraveler.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 Inktraveler.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.
inktraveler.com
Open Graph description is not detected on the main page of Inktraveler. 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: