4.9 sec in total
139 ms
4.6 sec
132 ms
Click here to check amazing LSJ Translatum content for Greece. Otherwise, check out these important facts you probably never knew about lsj.translatum.gr
The Liddell, Scott, Jones Ancient Greek Lexicon (LSJ) is perhaps the best known Ancient Greek-English dictionary. Here you can find a wiki implementation aiming to massively improve upon the dictionar...
Visit lsj.translatum.grWe analyzed Lsj.translatum.gr page load time and found that the first response time was 139 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
lsj.translatum.gr performance score
name
value
score
weighting
Value4.0 s
22/100
10%
Value4.5 s
37/100
25%
Value6.8 s
35/100
10%
Value640 ms
46/100
30%
Value0
100/100
15%
Value10.5 s
23/100
10%
139 ms
653 ms
616 ms
21 ms
922 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 20% of them (23 requests) were addressed to the original Lsj.translatum.gr, 12% (14 requests) were made to Scontent.xx.fbcdn.net and 11% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Lsj.translatum.gr.
Page size can be reduced by 184.0 kB (46%)
395.8 kB
211.8 kB
In fact, the total size of Lsj.translatum.gr main page is 395.8 kB. 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 192.5 kB which makes up the majority of the site volume.
Potential reduce by 41.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 41.4 kB or 68% of the original size.
Potential reduce by 11.4 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. LSJ Translatum images are well optimized though.
Potential reduce by 127.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 127.7 kB or 66% of the original size.
Potential reduce by 3.5 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. Lsj.translatum.gr needs all CSS files to be minified and compressed as it can save up to 3.5 kB or 82% of the original size.
Number of requests can be reduced by 63 (64%)
98
35
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LSJ Translatum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
lsj.translatum.gr
139 ms
Main_Page
653 ms
load.php
616 ms
gfdynamicfeedcontrol.css
21 ms
load.php
922 ms
plusone.js
59 ms
widgets.js
24 ms
show_ads.js
23 ms
jsapi
29 ms
gfdynamicfeedcontrol.js
22 ms
gfdynamicfeedcontrol.css
20 ms
gfdynamicfeedcontrol.js
28 ms
main-bg.jpg
8 ms
load.php
330 ms
load.php
333 ms
load.php
324 ms
cb=gapi.loaded_0
29 ms
main-bg.jpg
17 ms
shadow-left.gif
18 ms
header-line.gif
1547 ms
Agape.png
1581 ms
ca-pub-6539986036551354.js
46 ms
zrt_lookup.html
46 ms
show_ads_impl.js
56 ms
bg-header.gif
11 ms
border-bottom.gif
10 ms
nav-divider.gif
1650 ms
Logo.png
1620 ms
vertical-nav-divider.gif
18 ms
nav.gif
19 ms
list-bottom.png
22 ms
list-arrow.gif
21 ms
shadow-bottom.gif
26 ms
load.php
348 ms
load.php
406 ms
13 ms
default+en.css
39 ms
default+en.I.js
39 ms
ads
217 ms
expansion_embed.js
17 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
67 ms
cb=gapi.loaded_1
37 ms
fastbutton
105 ms
likebox.php
412 ms
osd.js
29 ms
ads
266 ms
postmessageRelay
75 ms
like.php
180 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
20 ms
cb=gapi.loaded_0
30 ms
cb=gapi.loaded_1
30 ms
grlryt2bdKIyfMSOhzd1eA.woff
40 ms
3193398744-postmessagerelay.js
29 ms
rpc:shindig_random.js
60 ms
cb=gapi.loaded_0
5 ms
css
103 ms
m_js_controller.js
51 ms
abg.js
87 ms
jot
173 ms
zwaoNywIX8f.js
120 ms
LVx-xkvaJ0b.png
118 ms
270 ms
bsredirect5.js
184 ms
ca
102 ms
favicon
81 ms
nessie_icon_thin_arrow_big_white.png
52 ms
s
45 ms
googlelogo_color_112x36dp.png
47 ms
x_button_blue2.svg
42 ms
ebiMDO3r-8l.css
17 ms
jGc-59L_9lo.css
21 ms
Pa4LYC3smxF.js
46 ms
FJmpeSpHpjS.js
100 ms
0wM5s1Khldu.js
99 ms
1bNoFZUdlYZ.js
99 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
10 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
10 ms
bst2tv3.html
152 ms
verifyc.js
63 ms
12039233_1050536278298592_2337918884049489450_n.jpg
49 ms
228469_214034671948761_6786928_n.jpg
22 ms
12814507_1042891149110520_6503302962913056486_n.jpg
29 ms
11245482_10206157798051421_7966237286558190091_n.jpg
28 ms
12717708_544827779014079_5073417619341914137_n.jpg
33 ms
10959497_774029982652696_8297843565103820265_n.jpg
34 ms
12801348_1123380934379334_5986794460540846392_n.jpg
34 ms
12036574_623167461173198_8572475968649000650_n.jpg
33 ms
11202082_495096130674726_339918552704206091_n.jpg
36 ms
423420_10151162818198816_444580227_n.jpg
45 ms
10354686_10150004552801856_220367501106153455_n.jpg
37 ms
12249832_844606695655947_2345048881089700228_n.jpg
36 ms
10277163_1391901877760648_7729905837453273353_n.jpg
44 ms
12234922_10153778324644297_2187793546875933502_n.jpg
39 ms
wL6VQj7Ab77.png
15 ms
s7jcwEQH7Sx.png
20 ms
clk
59 ms
I6-MnjEovm5.js
7 ms
pQrUxxo5oQp.js
8 ms
wt12578_728x90.gif
45 ms
lidar.js
4 ms
dvtp_src.js
146 ms
sbhK2lTE.js
24 ms
cTrvNaRi.html
11 ms
dvtp_src_internal26.js
53 ms
t2tv7.html
50 ms
visit.js
51 ms
avs5639.js
32 ms
event.gif
56 ms
event.jpg
29 ms
activeview
15 ms
activeview
17 ms
activeview
19 ms
Gfeeds
80 ms
ui
36 ms
lsj.translatum.gr 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-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
lsj.translatum.gr 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
lsj.translatum.gr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 doesn't use legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lsj.translatum.gr 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 Lsj.translatum.gr 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.
lsj.translatum.gr
Open Graph description is not detected on the main page of LSJ Translatum. 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: