68 sec in total
430 ms
56.8 sec
10.8 sec
Click here to check amazing Edinburgh News Scotsman content for United Kingdom. Otherwise, check out these important facts you probably never knew about edinburghnews.scotsman.com
An Edinburgh and Lothians' perspective on news, sport, what's on, lifestyle and more, from Scotland's capital city paper, the Edinburgh Evening News.
Visit edinburghnews.scotsman.comWe analyzed Edinburghnews.scotsman.com page load time and found that the first response time was 430 ms and then it took 67.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 28 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
edinburghnews.scotsman.com performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value4.8 s
30/100
25%
Value18.7 s
0/100
10%
Value5,150 ms
0/100
30%
Value0
100/100
15%
Value45.0 s
0/100
10%
430 ms
314 ms
1194 ms
450 ms
1018 ms
Our browser made a total of 148 requests to load all elements on the main page. We found that 11% of them (16 requests) were addressed to the original Edinburghnews.scotsman.com, 15% (22 requests) were made to Res.cloudinary.com and 7% (11 requests) were made to Fastlane.rubiconproject.com. The less responsive or slowest element that took the longest time to load (29 sec) relates to the external source Res.cloudinary.com.
Page size can be reduced by 5.1 MB (55%)
9.3 MB
4.2 MB
In fact, the total size of Edinburghnews.scotsman.com main page is 9.3 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. 85% 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. Javascripts take 4.7 MB which makes up the majority of the site volume.
Potential reduce by 703.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 703.4 kB or 89% of the original size.
Potential reduce by 148.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. Edinburgh News Scotsman images are well optimized though.
Potential reduce by 3.2 MB
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 3.2 MB or 69% of the original size.
Potential reduce by 1.0 MB
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. Edinburghnews.scotsman.com needs all CSS files to be minified and compressed as it can save up to 1.0 MB or 83% of the original size.
Number of requests can be reduced by 87 (78%)
111
24
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Edinburgh News Scotsman. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 73 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.edinburghnews.scotsman.com
430 ms
een-core.css
314 ms
slabs--responsive.css
1194 ms
app-een.css
450 ms
layout.css
1018 ms
jquery-1.11.3.min.js
1002 ms
jquery.bundle.min.js
371 ms
html5.bundle.min.js
1759 ms
css
2502 ms
eluminate.js
2501 ms
Bootstrap.js
2500 ms
jsapi
2359 ms
coremetrics-navigation.min.js
2356 ms
featured_business_list
2880 ms
jquery.cloudinary.min.js
2182 ms
native-ads-live.js
2880 ms
mobileBottomBannerStickyRes.js
2295 ms
janrain.min.js
2295 ms
init-login.js
2181 ms
footer.bundle.min.js
2232 ms
head.js
352 ms
50630000.js
29 ms
dispatcher-v3.js
851 ms
user-default.png
200 ms
serverComponent.php
224 ms
yahoo-min.js
1156 ms
cp-v3.js
117 ms
d7ab9538e8315dba47353dc3b24d4430.js
114 ms
82d28a91de2bf3293a56a2ee0717ebd1.js
54 ms
58e2a71dda76bb2b9e82c60f76bc6aaa.js
19 ms
7bce598ac23d82563420366d1e835751.js
18 ms
7df2bfb4547e8d57393672061af2d9cd.js
68 ms
c9a3b0bb8071649c76915b9d5a25448b.js
613 ms
c53ca308a1bc3542f2b069d4b8724247.js
613 ms
px.js
2855 ms
json-min.js
2680 ms
cm
4671 ms
cc.js
2548 ms
blt1kwh.js
2324 ms
front.asp
1724 ms
callback=itag.parseLotameAudiences
1632 ms
channels-jsonp.cgi
3048 ms
jpt
1527 ms
jpt
1529 ms
jpt
1819 ms
jpt
1528 ms
jpt
1255 ms
jpt
1545 ms
jpt
2231 ms
jpt
2231 ms
jpt
2230 ms
jpt
2230 ms
jpt
1981 ms
fastlane.json
2167 ms
fastlane.json
2413 ms
fastlane.json
2061 ms
fastlane.json
2167 ms
fastlane.json
1881 ms
fastlane.json
1262 ms
fastlane.json
2401 ms
fastlane.json
2667 ms
fastlane.json
2609 ms
fastlane.json
2605 ms
fastlane.json
2667 ms
publishertag.js
2029 ms
185246-267577554524813.js
147 ms
m
1146 ms
analytics.js
11888 ms
channels.cgi
5661 ms
loader.js
5220 ms
amzn_ads.js
11809 ms
gpt.js
11808 ms
ajax
6079 ms
var=ccauds
7680 ms
px.js
7679 ms
kormorant-1.27.23.min.js
10682 ms
async_usersync.html
7525 ms
image.jpg
15640 ms
image.jpg
15607 ms
image.jpg
15606 ms
image.jpg
0 ms
image.jpg
0 ms
image.jpg
0 ms
image.jpg
0 ms
image.jpg
28970 ms
image.jpg
28970 ms
image.jpg
28969 ms
image.jpg
28970 ms
image.jpg
28970 ms
image.jpg
29016 ms
image.jpg
29017 ms
image.jpg
29016 ms
image.jpg
23345 ms
image.jpg
23344 ms
image.jpg
23345 ms
image.jpg
23345 ms
image.jpg
23381 ms
image.jpg
23381 ms
image.jpg
23381 ms
d
0 ms
d
0 ms
d
0 ms
d
0 ms
d
0 ms
load.js
7971 ms
impl.271-68-RELEASE.js
3150 ms
beacon.js
3150 ms
plugin.js
7807 ms
mc.js
7789 ms
pubads_impl_147.js
22266 ms
bid
18050 ms
ca.png
20594 ms
pixel
0 ms
pixel
15868 ms
kormorant-1.27.23.min.css
5459 ms
cse.js
12016 ms
ca.png
0 ms
pmk-201545003.1.js
12643 ms
cse.js
17934 ms
m
14409 ms
large_images.jpg
15191 ms
login.johnstonpress.co.uk
13419 ms
analytics.js
11445 ms
css
5084 ms
wt
8050 ms
ads
8045 ms
wt
7734 ms
ads
7783 ms
large_images.jpg
9277 ms
large_images.jpg
9066 ms
ca.png
7457 ms
ca.png
6224 ms
cx.js
3473 ms
collect
2814 ms
analytics.js
2287 ms
collect
1574 ms
collect
2267 ms
en-US
1468 ms
wt
289 ms
wt
251 ms
chartbeat.js
1281 ms
p1.html
533 ms
p1.js
762 ms
jsapi
905 ms
capture:login
637 ms
ping
300 ms
rep.gif
677 ms
events
617 ms
edinburghnews.scotsman.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
edinburghnews.scotsman.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
edinburghnews.scotsman.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
Image elements do not have [alt] attributes
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 Edinburghnews.scotsman.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 Edinburghnews.scotsman.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.
edinburghnews.scotsman.com
Open Graph description is not detected on the main page of Edinburgh News Scotsman. 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: