10.9 sec in total
496 ms
8 sec
2.4 sec
Welcome to tellscore.com homepage info - get ready to check Tellscore best content for Thailand right away, or after learning these important things about tellscore.com
Tellscore, where influencing storytellers meet brands and products. Millions of people are reachable via Tellscore's micro influencers.
Visit tellscore.comWe analyzed Tellscore.com page load time and found that the first response time was 496 ms and then it took 10.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
tellscore.com performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value17.2 s
0/100
25%
Value17.1 s
0/100
10%
Value5,710 ms
0/100
30%
Value0.016
100/100
15%
Value25.4 s
0/100
10%
496 ms
961 ms
3400 ms
33 ms
52 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Tellscore.com, 49% (52 requests) were made to D1ee0vqmjhj8pf.cloudfront.net and 37% (39 requests) were made to Th.tellscore.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Th.tellscore.com.
Page size can be reduced by 994.5 kB (39%)
2.6 MB
1.6 MB
In fact, the total size of Tellscore.com main page is 2.6 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. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 857.1 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 857.1 kB or 74% of the original size.
Potential reduce by 137.3 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. Tellscore images are well optimized though.
Potential reduce by 137 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 17 (39%)
44
27
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tellscore. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
tellscore.com
496 ms
tellscore.com
961 ms
3400 ms
modernizr.min.js
33 ms
detectizr.min.js
52 ms
notch-detected-event.min.js
683 ms
gtm.js
104 ms
logo-white-ts.9ee81d0.svg
303 ms
influencer-signup-icon.23d3ff9.png
547 ms
marketer-signup-icon.4a58454.png
780 ms
global-language.4a82ad9.svg
826 ms
ios-en.c48e8a0.svg
777 ms
android-en.7b77464.svg
780 ms
facebook.af3be8c.svg
784 ms
twitter.9ec32c9.svg
847 ms
instagram.7fc4eef.svg
1006 ms
youtube.bb7e96c.svg
1010 ms
big-world.8aa7842.png
1715 ms
banner-influencer@2x.3e991ab.png
2366 ms
influencer-icon.abf46a2.svg
1056 ms
banner-marketer@2x.dba993e.png
1077 ms
marketer-icon.39d1169.svg
1278 ms
banner-about-mobile@2x.b3f9c8a.png
1914 ms
Prompt-SemiBold.3df2cb7.ttf
1743 ms
Prompt-Bold.bc0acd8.ttf
1297 ms
Prompt-ExtraBold.c742aaf.ttf
1725 ms
Prompt-Medium.e5b348d.ttf
1535 ms
Prompt-Regular.b338ce0.ttf
1783 ms
Prompt-Light.f863613.ttf
1954 ms
Prompt-ExtraLight.8ff5b11.ttf
2191 ms
js
176 ms
fbevents.js
133 ms
354 ms
analytics.js
361 ms
uwt.js
385 ms
events.js
407 ms
f78ca8d05dd211eea69df365e7540b83.png
404 ms
icon-reel.9e469fb.svg
1802 ms
icon-video.3f48ce2.svg
1850 ms
icon-photo.3fe0033.svg
1944 ms
faq.c3c9c08.jpg
2231 ms
hyhm.2208946.jpg
2946 ms
logo.f42c96b.svg
2074 ms
8d5a2ce02f5b11edb047774de142a47c.png
353 ms
8f9274302f5c11edb047774de142a47c.png
2030 ms
96dbc6502f5311edb047774de142a47c.png
351 ms
3b8e46702f5c11edb047774de142a47c.png
352 ms
39035460cff811ea8748992836cae02a.png
378 ms
65a605654a9e5.jpg
359 ms
65a605e365172.jpg
1798 ms
65a629dce9683.png
360 ms
65a643bc80cac.png
387 ms
65a60327da635.jpg
361 ms
65a604e857a79.jpg
387 ms
63e1bfa7790bf.jpeg
414 ms
63e1bf9dbc143.png
413 ms
63ce0c00016d2.jpg
417 ms
63ce0be72eccf.png
411 ms
63468d5cc8412.jpg
430 ms
63468d6d62f81.png
416 ms
6298334acc3b6.jpg
428 ms
62983324c3e87.png
422 ms
625f70343aaae.jpg
425 ms
625f707ee9556.png
1389 ms
625504f0793c7.png
435 ms
625505a7d4780.jpeg
434 ms
62f4ad45c2bc9.jpeg
435 ms
62f4ad53b9f7e.jpeg
446 ms
62f4ad5a4d843.jpeg
442 ms
62f4adac782a3.jpeg
443 ms
62f4afae6f8aa.png
447 ms
62f48d5c7aafc.jpeg
1870 ms
62f48d64a3e42.jpeg
464 ms
62f48d6cefd1f.jpeg
459 ms
62f4911d08d30.jpeg
464 ms
62c645e2e34c2.jpeg
472 ms
62c645ebdf2a4.png
476 ms
62c645f323c48.png
483 ms
88 ms
collect
37 ms
adsct
174 ms
adsct
159 ms
62c646861332d.jpeg
137 ms
62c554a0278ee.jpeg
139 ms
62c554a961940.jpeg
142 ms
62c554afc3229.jpeg
141 ms
62c554bc1c4be.jpeg
143 ms
62c5557972641.png
144 ms
62b5736e8efc6.jpeg
151 ms
62b573760671f.jpeg
134 ms
62b57381b6ec3.png
134 ms
4b6170f.js
1818 ms
2c3563d.js
1831 ms
7d5d1b6.js
1929 ms
a03ae79.js
1987 ms
9bb5dc1.js
2186 ms
994f5f7.js
2226 ms
85c670c.js
3083 ms
2f5f53c.js
2592 ms
62b573897bf27.png
121 ms
62b57418a6e4a.png
114 ms
62b56a1890af1.JPG
130 ms
62b56a22cacdf.JPG
135 ms
62b56a2986397.JPG
136 ms
62b56a30a23f4.JPG
136 ms
62b56a968bd0d.jpeg
142 ms
tellscore.com 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.
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
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.
tellscore.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
Missing source maps for large first-party JavaScript
tellscore.com 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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tellscore.com 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 Tellscore.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.
tellscore.com
Open Graph description is not detected on the main page of Tellscore. 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: