4.3 sec in total
323 ms
3.5 sec
418 ms
Welcome to my-history.co.uk homepage info - get ready to check My History best content for United Kingdom right away, or after learning these important things about my-history.co.uk
Genealogy specialist of family tree software, chart printing, archive safe folders and storage boxes, trade directories, binders and blank charts
Visit my-history.co.ukWe analyzed My-history.co.uk page load time and found that the first response time was 323 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
my-history.co.uk performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value5.7 s
16/100
25%
Value5.4 s
56/100
10%
Value740 ms
40/100
30%
Value0.279
43/100
15%
Value10.2 s
25/100
10%
323 ms
623 ms
300 ms
413 ms
314 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 62% of them (44 requests) were addressed to the original My-history.co.uk, 8% (6 requests) were made to A1.awin1.com and 4% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain My-history.co.uk.
Page size can be reduced by 530.7 kB (28%)
1.9 MB
1.4 MB
In fact, the total size of My-history.co.uk main page is 1.9 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. 35% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 49.0 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 49.0 kB or 79% of the original size.
Potential reduce by 66.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. My History images are well optimized though.
Potential reduce by 248.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 248.5 kB or 65% of the original size.
Potential reduce by 166.3 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. My-history.co.uk needs all CSS files to be minified and compressed as it can save up to 166.3 kB or 86% of the original size.
Number of requests can be reduced by 11 (17%)
63
52
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My History. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
my-history.co.uk
323 ms
www.my-history.co.uk
623 ms
actinic.css
300 ms
jquery-1.11.1.min.js
413 ms
jquery.bxslider.min.js
314 ms
jquery.bxslider.css
219 ms
sellerdeck.min.js
544 ms
jquery-ui-1.10.1.tabs.min.js
334 ms
tabberv4support.js
410 ms
multiotherinfosupport-v3.js
504 ms
conversion.js
14 ms
tracker.js
64 ms
fbevents.js
64 ms
148 ms
146575.jpg
555 ms
image-1759515-10660744-1403197734000
204 ms
image-1759515-10391801-1403197734000
220 ms
pp-acceptance-medium.png
145 ms
homepage-icon.png
214 ms
my-account.png
213 ms
cart-icon.png
230 ms
checkout-icon.png
237 ms
MyHistoryNewSiteLogo352.png
387 ms
SpringBackBinder_700x150.jpg
522 ms
ArchiveBinder_700x150.jpg
623 ms
DataCDs_700x150.jpg
639 ms
Charts_700x150.jpg
663 ms
ChartsGen_700x150.jpg
674 ms
FTS_700x150.jpg
905 ms
Ancestor_300.jpg
847 ms
Archie350x150.jpg
945 ms
LargeChartOnWall350x150.jpg
1127 ms
Recording350x150.jpg
1109 ms
Researching350x150.jpg
977 ms
cshow.gif
437 ms
workingchart1.jpg
1479 ms
4_binders_fanned400.jpg
1298 ms
FH6Box_400.jpg
1252 ms
FH5_box_left_300.jpg
1287 ms
Certificate_Pocket_350.jpg
1427 ms
PhotoCorner1.3.jpg
1534 ms
Post%20Card.JPG
1641 ms
UTP0263.jpg
1796 ms
LAN1825BN300.jpg
1602 ms
A37Ped500.jpg
1746 ms
Window-Springback%20Binder-400.jpg
2012 ms
twitter_logo.jpg
505 ms
Facebook_logo.jpg
531 ms
British-Newspaper-Archive.gif
644 ms
131943.jpg
620 ms
search-icon.png
1728 ms
ga.js
15 ms
1613999695582919
81 ms
__utm.gif
66 ms
bx_loader.gif
1688 ms
bx_controls.png
1733 ms
pv
127 ms
100 ms
110 ms
collect
75 ms
10660744-1417803189360
330 ms
38 ms
ga-audiences
14 ms
logo
380 ms
beginsearch_468x60.gif
27 ms
fmpau-generic-468x60.gif
25 ms
genesreunited120x60.png
12 ms
english_heritage_leader_468x60.gif
31 ms
fmp-logo-120x60_3.gif
100 ms
english_heritage_sky_160x600.gif
28 ms
logo
208 ms
my-history.co.uk 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Form elements do not have associated labels
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.
my-history.co.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
my-history.co.uk SEO score
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
![]()
EN
![]()
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise My-history.co.uk can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that My-history.co.uk main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
my-history.co.uk
Open Graph description is not detected on the main page of My History. 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: