5.4 sec in total
333 ms
4.7 sec
358 ms
Visit scriptum.ro now to see the best up-to-date Scriptum content for Romania and also check out these interesting facts you probably never knew about scriptum.ro
Libraria Scriptum
Visit scriptum.roWe analyzed Scriptum.ro page load time and found that the first response time was 333 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
scriptum.ro performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value7.3 s
5/100
25%
Value18.1 s
0/100
10%
Value6,830 ms
0/100
30%
Value0.674
8/100
15%
Value30.7 s
0/100
10%
333 ms
2739 ms
268 ms
36 ms
186 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 85% of them (80 requests) were addressed to the original Scriptum.ro, 3% (3 requests) were made to Static.olark.com and 2% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Scriptum.ro.
Page size can be reduced by 504.6 kB (47%)
1.1 MB
563.7 kB
In fact, the total size of Scriptum.ro main page is 1.1 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. 60% of websites need less resources to load. Images take 472.7 kB which makes up the majority of the site volume.
Potential reduce by 65.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. This page needs HTML code to be minified as it can gain 9.1 kB, which is 11% 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 65.2 kB or 81% of the original size.
Potential reduce by 24.5 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. Scriptum images are well optimized though.
Potential reduce by 326.9 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 326.9 kB or 80% of the original size.
Potential reduce by 88.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. Scriptum.ro needs all CSS files to be minified and compressed as it can save up to 88.0 kB or 83% of the original size.
Number of requests can be reduced by 39 (43%)
91
52
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Scriptum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
scriptum.ro
333 ms
www.scriptum.ro
2739 ms
base-librarie.css
268 ms
prototype.js
36 ms
custom.css
186 ms
style.css
237 ms
facebookfree.css
223 ms
j2t-rewardpoints.css
190 ms
j2t_rewardsocial.css
197 ms
catalogsale.css
287 ms
ccard.js
288 ms
validation.js
288 ms
builder.js
313 ms
effects.js
323 ms
dragdrop.js
349 ms
controls.js
353 ms
js.js
366 ms
form.js
377 ms
translate.js
421 ms
cookies.js
411 ms
modernizr.js
440 ms
product.js
437 ms
configurable.js
449 ms
j2t_giftvoucher.js
480 ms
carousel.js
499 ms
bundle.js
581 ms
jquery.min.js
42 ms
jquery.defaultvalue.js
519 ms
jquery.hoverintent.js
522 ms
jquery.lightbox_me.js
530 ms
jquery.waypoints.js
569 ms
jquery.slides.js
600 ms
jquery.bbq.js
618 ms
catalog-ajax.js
617 ms
main.js
618 ms
jquery.pjax.js
682 ms
catalog.js
681 ms
bg1.jpg
381 ms
ga.js
36 ms
sprites.png
256 ms
mutat-buton.jpg
128 ms
logo_2.jpg
126 ms
fb.gif
154 ms
sprite.png
189 ms
bonhoeffer-mare.jpg
407 ms
taxe-postale-gratuite-scriptum_3.jpg
484 ms
simplifica_1.jpg
327 ms
lucado-reducere1.jpg
411 ms
reduceri-scriptum-mic_1.jpg
340 ms
voucher-banner-mic_4.jpg
346 ms
puncte-fidelitate-mic_4.jpg
424 ms
hristos-painea_noastra.jpg
429 ms
la-izvoarele-luminii.jpg
428 ms
alergarea_staruitoare.jpg
496 ms
poezii_de_paste.jpg
494 ms
hristos-marturia_mea_1_1.jpg
548 ms
intelepciune_scriptum.jpg
520 ms
arata-mi_scriptum.jpg
538 ms
bonhoeffer-metaxas.jpg
599 ms
imparati.jpg
587 ms
o-tara-ideala.jpg
596 ms
eul-din-spatele-mastii-_1_.jpg
618 ms
flacara-iubirii.jpg
629 ms
bunatate-adevar-dreptate.jpg
644 ms
da-sens-vietii.jpg
679 ms
portretul-predicatorului.jpg
695 ms
scriptum_manifest.jpg
693 ms
puterea-numelui-sau.jpg
742 ms
am-fost-acolo.jpg
728 ms
increderea-in-dumnezeu.jpg
749 ms
claudia.jpg
768 ms
__utm.gif
12 ms
visa.png
715 ms
mastercard.png
723 ms
collect
93 ms
all.js
34 ms
loader0.js
96 ms
paypal.png
709 ms
discover.png
717 ms
amex.png
728 ms
facebook-large.png
746 ms
141 ms
xd_arbiter.php
25 ms
xd_arbiter.php
43 ms
twitter-large.png
744 ms
youtube-large.png
703 ms
2719-897-10-9079.js
209 ms
stars.png
661 ms
arrow-up.png
604 ms
slider-prev.png
616 ms
slider-next.png
641 ms
c
114 ms
application2.js
103 ms
ping
57 ms
scriptum.ro accessibility score
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
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
scriptum.ro 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
Page has valid source maps
scriptum.ro SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
RO
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Scriptum.ro can be misinterpreted by Google and other search engines. Our service has detected that Romanian is used on the page, and it does not match the claimed English language. Our system also found out that Scriptum.ro 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.
scriptum.ro
Open Graph description is not detected on the main page of Scriptum. 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: