3.2 sec in total
128 ms
2.4 sec
585 ms
Click here to check amazing CORE content for Indonesia. Otherwise, check out these important facts you probably never knew about core.ac.uk
The world’s largest collection of open access research papers
Visit core.ac.ukWe analyzed Core.ac.uk page load time and found that the first response time was 128 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
core.ac.uk performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value44.9 s
0/100
25%
Value6.1 s
44/100
10%
Value7,550 ms
0/100
30%
Value0.281
43/100
15%
Value26.0 s
0/100
10%
128 ms
409 ms
20 ms
24 ms
17 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 89% of them (64 requests) were addressed to the original Core.ac.uk, 8% (6 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Core.ac.uk.
Page size can be reduced by 92.3 kB (21%)
440.6 kB
348.4 kB
In fact, the total size of Core.ac.uk main page is 440.6 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. Only a small number of websites need less resources to load. Images take 361.6 kB which makes up the majority of the site volume.
Potential reduce by 60.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 60.4 kB or 76% of the original size.
Potential reduce by 31.9 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. CORE images are well optimized though.
Number of requests can be reduced by 23 (36%)
64
41
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CORE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
core.ac.uk
128 ms
core.ac.uk
409 ms
9c2faca1b4ac1f89a397.css
20 ms
d1bc6b13e2cde38f9ff9.css
24 ms
85ffa2540d2f83109449.css
17 ms
e910be9769c9da8415d7.css
22 ms
css
32 ms
database.svg
279 ms
community.svg
343 ms
homeServices.svg
329 ms
globe.svg
270 ms
gears.svg
267 ms
building.svg
421 ms
neural.svg
545 ms
posi-7077ad96cde68258c6d398773c2cd102.svg
537 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
36 ms
KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf
49 ms
KFOlCnqEu92Fr1MmWUlfBBc9AMP6lQ.ttf
50 ms
polyfills-48c9779831b86ca1584a.js
630 ms
webpack-6b368952efa9e41ab8d1.js
403 ms
framework.898ed9c4190ec62ba669.js
405 ms
commons.d7ddf4d2b1bef08d6a43.js
404 ms
main-b7df5304ee374402e059.js
405 ms
b5f2ed29.441239f4fc365a69741a.js
406 ms
e82996df.86a4b1a61816698443e2.js
407 ms
e123cc9a915d464f25c3a1ad4bef65b0346274d4.1fb3effd090b2cf229c2.js
408 ms
f015f7548453644a0f506f43332d5631f4b2be71.fbe1fed265d74b60858b.js
407 ms
aa49bba4ade0b43da950ed91bfedf5d75bdf5088.a1db0dcf1f61b484c7e8.js
407 ms
aa49bba4ade0b43da950ed91bfedf5d75bdf5088_CSS.ddce25b62cf34b951439.js
409 ms
88941b492ac9740506eefed5aee5c711061c8dc8.ae093e90d5f38d3f1f45.js
411 ms
2b1ce4494ef86e25ac6935f103a992cb8279131f.d9558af2faaffeeb09b3.js
411 ms
_app-9e398c8279da43429773.js
422 ms
87599ed0f6d6993debe6eabc808b0761f5570441.60d8cc8cc4bd99281c99.js
435 ms
87599ed0f6d6993debe6eabc808b0761f5570441_CSS.34e373399cdc573d23ed.js
411 ms
index-76edcbece27daf398f64.js
413 ms
_buildManifest.js
414 ms
_ssgManifest.js
422 ms
vcd15cbe7772f49c399c6a5babf22c1241717689176015
57 ms
data-provider.svg
781 ms
membership.svg
785 ms
server.svg
793 ms
oai.svg
806 ms
line.424b4032ca9d90aee4b9193ce1006200.svg
525 ms
turnitin.png
807 ms
open-university.png
913 ms
mooc-founder.png
927 ms
research-england.png
928 ms
KFOkCnqEu92Fr1Mu51xIIzcXKMny.ttf
3 ms
KFOjCnqEu92Fr1Mu51TjASc6CsHYl4BO.ttf
15 ms
KFOjCnqEu92Fr1Mu51TzBic6CsHYl4BO.ttf
16 ms
server-status.svg
704 ms
search-engine.svg
811 ms
time-management.svg
767 ms
Gareth_Malcolm.jpeg
788 ms
account.93a73dbe5761da80435ee3e87b5575ab.svg
544 ms
nvidia.svg
807 ms
anthropic.svg
813 ms
grammarly.svg
839 ms
lean.svg
925 ms
naver.svg
958 ms
kathleen.svg
1063 ms
cambridge.svg
1084 ms
oxford.svg
1090 ms
chica.svg
1101 ms
stAndrews.svg
1191 ms
imperial.svg
1220 ms
johnson.jpg
1328 ms
coar.svg
1333 ms
sparc.png
1343 ms
researchInovation.svg
1367 ms
losAlamos.svg
1447 ms
jisc.svg
1481 ms
core.ac.uk 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
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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>).
core.ac.uk 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
core.ac.uk 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
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 Core.ac.uk 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 Core.ac.uk 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.
core.ac.uk
Open Graph description is not detected on the main page of CORE. 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: