10 sec in total
97 ms
9.3 sec
550 ms
Welcome to josesandin.com homepage info - get ready to check Josesandin best content right away, or after learning these important things about josesandin.com
Simultaneous translation company in Madrid. Interpreters and equipment for conferences and meetings. Spanish, English, French, and more.
Visit josesandin.comWe analyzed Josesandin.com page load time and found that the first response time was 97 ms and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
josesandin.com performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value9.1 s
1/100
25%
Value9.6 s
11/100
10%
Value820 ms
35/100
30%
Value0.136
80/100
15%
Value13.7 s
11/100
10%
97 ms
1372 ms
304 ms
346 ms
326 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 91% of them (123 requests) were addressed to the original Josesandin.com, 6% (8 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Josesandin.com.
Page size can be reduced by 137.4 kB (7%)
1.9 MB
1.8 MB
In fact, the total size of Josesandin.com main page is 1.9 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. Javascripts take 992.7 kB which makes up the majority of the site volume.
Potential reduce by 110.4 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 110.4 kB or 80% of the original size.
Potential reduce by 14.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. Josesandin images are well optimized though.
Potential reduce by 5.1 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. This website has mostly compressed JavaScripts.
Potential reduce by 7.7 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. Josesandin.com has all CSS files already compressed.
Number of requests can be reduced by 90 (74%)
122
32
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Josesandin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 68 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
josesandin.com
97 ms
1372 ms
tsvg-block.css
304 ms
style.min.css
346 ms
styles.css
326 ms
tsvg-fonts.css
319 ms
style-frontend-pro.css
327 ms
bootstrap.min.css
335 ms
font-awesome.min.css
612 ms
flaticon-set.css
636 ms
magnific-popup.css
633 ms
owl.carousel.min.css
634 ms
owl.theme.default.min.css
635 ms
animate.css
644 ms
bootsnav.css
916 ms
style.css
938 ms
responsive.css
943 ms
css
40 ms
css
58 ms
style.css
945 ms
css
64 ms
js_composer.min.css
958 ms
lodash.min.js
950 ms
regenerator-runtime.min.js
1223 ms
wp-polyfill.min.js
1243 ms
react.min.js
1243 ms
react-dom.min.js
1252 ms
dom-ready.min.js
1258 ms
hooks.min.js
1260 ms
i18n.min.js
1528 ms
a11y.min.js
1553 ms
url.min.js
1552 ms
api-fetch.min.js
1559 ms
blob.min.js
1555 ms
autop.min.js
1563 ms
block-serialization-default-parser.min.js
1831 ms
deprecated.min.js
1863 ms
dom.min.js
1864 ms
escape-html.min.js
1864 ms
element.min.js
1866 ms
js
62 ms
style.css
1867 ms
tooltip.css
1839 ms
swiper-bundle.min.css
1862 ms
rs6.css
1851 ms
is-shallow-equal.min.js
1849 ms
keycodes.min.js
1840 ms
priority-queue.min.js
1842 ms
compose.min.js
1854 ms
redux-routine.min.js
1852 ms
data.min.js
1858 ms
html-entities.min.js
1854 ms
shortcode.min.js
1860 ms
blocks.min.js
1861 ms
moment.min.js
1667 ms
date.min.js
1855 ms
primitives.min.js
1851 ms
rich-text.min.js
1858 ms
warning.min.js
1854 ms
components.min.js
1674 ms
keyboard-shortcuts.min.js
1671 ms
notices.min.js
1721 ms
token-list.min.js
1858 ms
wordcount.min.js
1846 ms
block-editor.min.js
1876 ms
server-side-render.min.js
1851 ms
index.js
1673 ms
jquery.min.js
1727 ms
jquery-migrate.min.js
1856 ms
email-decode.min.js
1554 ms
index.js
1965 ms
index.js
1961 ms
rbtools.min.js
1424 ms
rs6.min.js
1663 ms
front-end-free.js
1781 ms
bootstrap.min.js
1775 ms
equal-height.min.js
1848 ms
jquery.appear.js
1853 ms
jquery.easing.min.js
1601 ms
jquery.magnific-popup.min.js
1663 ms
modernizr.custom.13711.js
1580 ms
owl.carousel.min.js
1773 ms
wow.min.js
1839 ms
progress-bar.min.js
1848 ms
isotope.pkgd.min.js
1589 ms
imagesloaded.pkgd.min.js
1583 ms
count-to.js
1660 ms
bootsnav.js
1767 ms
main.js
1830 ms
js_composer_front.min.js
1833 ms
popper.min.js
1574 ms
tooltip.js
1708 ms
swiper-bundle.min.js
1663 ms
main.js
1678 ms
preloader.svg
1133 ms
logo-josesandin-1.png
1194 ms
Traduccion-simultanea-Madrid-ponente-3.jpg
1407 ms
Traductores-simultaneos-Madrid-4.png
1344 ms
In-Out-Travel-185x119.png
1323 ms
Movimiento-contra-la-Intolerancia-185x119.jpg
1339 ms
Alsa-185x119.jpg
1427 ms
Loccitane-185x119.jpg
1498 ms
UNIR-185x119.png
1627 ms
Exide-185x119.jpg
1646 ms
Logo_lycee-francais-de-madrid-2-2-185x119.png
1665 ms
NWWAC-185x119.jpeg
1713 ms
Liujo-185x119.jpg
1664 ms
Institut-francais-185x119.jpg
1536 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
60 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
77 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
122 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
124 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
125 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
124 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
122 ms
pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf
124 ms
fa-solid-900.woff
2029 ms
fa-regular-400.woff
1935 ms
fa-brands-400.woff
1951 ms
Aneca-185x119.jpg
1766 ms
Reporteros-sin-fronteras-185x119.jpg
1742 ms
Groupe-Adeo-185x119.jpg
1774 ms
Ehlers-Danlos-Society-185x119.png
1992 ms
European-Medical-Simulation-185x119.jpg
2014 ms
Ministerio-Inclusion-Seguridad-Social-Migraciones-2-185x119.jpg
1926 ms
TVE-185x119.png
1863 ms
Leroy-Merlin-Logo-2-185x119.png
1846 ms
WWF-3-185x119.jpg
1870 ms
advisory_board_company-185x119.png
1993 ms
arrow-left.svg
2013 ms
arrow-right.svg
1984 ms
Interpretes-simultaneos-Madrid-2.jpg
2088 ms
TVE-interpretes-1.png
2097 ms
Reporteros-sin-Fronteras-Traductores-simultaneos-1.png
2124 ms
Canal-24-horas-interpretes-1.png
2193 ms
josesandin.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
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
josesandin.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
Missing source maps for large first-party JavaScript
josesandin.com 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
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 Josesandin.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 Josesandin.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.
josesandin.com
Open Graph data is detected on the main page of Josesandin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: