2.8 sec in total
193 ms
2.2 sec
422 ms
Click here to check amazing James Innes content for Nigeria. Otherwise, check out these important facts you probably never knew about jamesinnes.group
James Innes Group's team of CV/Resume writers and career experts deliver job winning results through its range of CV/Resume writing, coaching and personal professional branding services.
Visit jamesinnes.groupWe analyzed Jamesinnes.group page load time and found that the first response time was 193 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
jamesinnes.group performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value3.2 s
71/100
25%
Value3.3 s
91/100
10%
Value960 ms
29/100
30%
Value0.012
100/100
15%
Value8.2 s
41/100
10%
193 ms
888 ms
64 ms
107 ms
47 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 9% of them (4 requests) were addressed to the original Jamesinnes.group, 36% (16 requests) were made to Cdn.jamesinnes.group and 30% (13 requests) were made to Embed.tawk.to. The less responsive or slowest element that took the longest time to load (888 ms) belongs to the original domain Jamesinnes.group.
Page size can be reduced by 64.8 kB (22%)
290.1 kB
225.3 kB
In fact, the total size of Jamesinnes.group main page is 290.1 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. 50% of websites need less resources to load. Javascripts take 175.1 kB which makes up the majority of the site volume.
Potential reduce by 41.3 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.3 kB or 79% of the original size.
Potential reduce by 0 B
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. James Innes images are well optimized though.
Potential reduce by 23.5 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 23.5 kB or 13% of the original size.
Number of requests can be reduced by 22 (54%)
41
19
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of James Innes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
jamesinnes.group
193 ms
jamesinnes.group
888 ms
gtm.js
64 ms
Index.css
107 ms
6152da084e.js
47 ms
cookiebar-latest.min.js
22 ms
core.js
236 ms
js
48 ms
js
133 ms
animate.min.css
28 ms
css2
33 ms
css
115 ms
James_Innes_Group_Logo_Dark.svg
201 ms
james-innes-group-chibi-spaceman.png
512 ms
james-innes-profile-picture.webp
209 ms
logo-bbc.webp
207 ms
logo-the-guardian.webp
207 ms
logo-the-telegraph.webp
208 ms
logo-sky-news.webp
208 ms
LIVE_1646382020434_18bbf386-51ac-4922-98eb-b2f498d651ca.webp
216 ms
LIVE_1646377534833_42fb0e15-2a88-4870-9424-452959152c1d.webp
217 ms
LIVE_1653486451123_9d00fb0e-a95c-4f84-a916-e52039d1cea3.webp
520 ms
LIVE_1621867039039_b8d1ff10-197b-4e3d-91a3-e6946e4cf285.webp
215 ms
LIVE_1654589204303_d496a040-e50b-442b-9ede-cfc12fa65331.webp
225 ms
LIVE_1678874038634_d04da72e-07eb-4d1b-b9a6-10be9b719bc1.webp
224 ms
LIVE_1657111572752_ff773c31-8e02-4faa-a8b9-51a3fb91c234.webp
518 ms
LIVE_1653911389810_a088a7a3-d45e-4966-b512-3ef467250ef4.webp
224 ms
space-telephone.webp
226 ms
cookiebar-flying.min.css
181 ms
en.html
193 ms
1faih946b
283 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
38 ms
twk-arr-find-polyfill.js
172 ms
twk-object-values-polyfill.js
55 ms
twk-event-polyfill.js
201 ms
twk-entries-polyfill.js
183 ms
twk-iterator-polyfill.js
180 ms
twk-promise-polyfill.js
232 ms
twk-main.js
109 ms
twk-vendor.js
261 ms
twk-chunk-vendors.js
294 ms
twk-chunk-common.js
193 ms
twk-runtime.js
229 ms
twk-app.js
208 ms
jamesinnes.group 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
Buttons do not have an accessible name
Links do not have a discernible name
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
jamesinnes.group 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
Browser errors were logged to the console
Page has valid source maps
jamesinnes.group SEO score
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 Jamesinnes.group 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 Jamesinnes.group 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.
jamesinnes.group
Open Graph description is not detected on the main page of James Innes. 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: