5.9 sec in total
532 ms
4 sec
1.4 sec
Visit sovrin.com now to see the best up-to-date Sovrin content and also check out these interesting facts you probably never knew about sovrin.com
Injection moulding of precision components is our core business and one which we have excelled at for over fifty five years.
Visit sovrin.comWe analyzed Sovrin.com page load time and found that the first response time was 532 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
sovrin.com performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value14.8 s
0/100
25%
Value20.4 s
0/100
10%
Value10,310 ms
0/100
30%
Value0.031
100/100
15%
Value20.3 s
2/100
10%
532 ms
132 ms
218 ms
262 ms
250 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 82% of them (70 requests) were addressed to the original Sovrin.com, 9% (8 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (941 ms) belongs to the original domain Sovrin.com.
Page size can be reduced by 566.8 kB (6%)
9.9 MB
9.4 MB
In fact, the total size of Sovrin.com main page is 9.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. 75% 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. Images take 8.9 MB which makes up the majority of the site volume.
Potential reduce by 345.9 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 345.9 kB or 89% of the original size.
Potential reduce by 215.3 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. Sovrin images are well optimized though.
Potential reduce by 1.7 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 4.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. Sovrin.com has all CSS files already compressed.
Number of requests can be reduced by 36 (47%)
76
40
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sovrin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
sovrin.com
532 ms
wp-emoji-release.min.js
132 ms
styles.css
218 ms
rs6.css
262 ms
cookieblocker.min.css
250 ms
font-awesome.min.css
252 ms
font-awesome-v4-shims.min.css
254 ms
theme-style.min.css
422 ms
style.basic.css
258 ms
style-underline.css
288 ms
wpb-grid.min.css
294 ms
ext-style.min.css
290 ms
js_composer.min.css
386 ms
css
39 ms
widget.js
346 ms
jquery.min.js
456 ms
jquery-migrate.min.js
385 ms
rbtools.min.js
468 ms
rs6.min.js
525 ms
js
65 ms
css
35 ms
css
35 ms
index.js
465 ms
index.js
486 ms
extras.min.js
654 ms
main.min.js
589 ms
googlesitekit-consent-mode-3d6495dceaebc28bcca3.js
589 ms
asl-prereq.js
590 ms
asl-core.js
590 ms
asl-results-vertical.js
652 ms
asl-autocomplete.js
683 ms
asl-load.js
651 ms
asl-wrapper.js
683 ms
ext-extras.min.js
651 ms
ext-elements.min.js
737 ms
wp-consent-api.min.js
742 ms
complianz.min.js
741 ms
js_composer_front.min.js
736 ms
gtm.js
66 ms
Sovrin_logo.svg
202 ms
Sovrin_logo_white.svg
208 ms
AXH29659.jpg
622 ms
AXH28634.jpg
622 ms
Sovrin_blue_room.jpg
462 ms
Relenza-cropped-Phase1-030929-scaled.jpg
624 ms
AXH28496.jpg
540 ms
AWP_1284.jpg
794 ms
hero-overlay.svg
550 ms
hero-widget-blue-longer.svg
625 ms
Sovrin-37-560x560.jpg
636 ms
Picture4.png
713 ms
Imigran-560x560.jpg
708 ms
ALARISdebadged-560x560.jpg
711 ms
CVBlistersLong-2-560x413.jpg
713 ms
Sovrin-32-560x560.jpg
723 ms
AlarisEnteral-560x747.jpg
794 ms
Lord-560x747.jpg
798 ms
MyDay-560x747.jpg
798 ms
Relenza-560x747.jpg
800 ms
ImigranWide-560x747.jpg
810 ms
bsc_member-logo_on-white_cmyk_0.svg
845 ms
BSI-ISO13485-300x139.png
847 ms
Manufacture-2030-Badge.svg
847 ms
AWP_1352-1920x1280.jpg
852 ms
case-studies-Ophthalmics-Packaging-1920x1258.jpg
851 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhLsWkANDM.ttf
92 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhHMWkANDM.ttf
106 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhcMWkANDM.ttf
117 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhrsWkANDM.ttf
118 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhLsSkANDM.ttf
119 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduh8MKkANDM.ttf
119 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhycKkANDM.ttf
118 ms
Location-1721-1920x1280.jpg
791 ms
AXH29966Wide.jpg
880 ms
AXH29894.jpg
933 ms
Sovrin_precision-1920x1274.jpg
850 ms
AXH29769.jpg
941 ms
Sovrin_building-e1697833988818-1920x1436.jpg
861 ms
P.svg
799 ms
E.svg
878 ms
M.svg
878 ms
F.svg
880 ms
widget_iframe.2b2d73daf636805223fb11d48f3e94f7.html
37 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
8 ms
settings
104 ms
sovrin.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.
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
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>).
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.
sovrin.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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
sovrin.com 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
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 Sovrin.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 Sovrin.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.
sovrin.com
Open Graph data is detected on the main page of Sovrin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: