17.4 sec in total
1.2 sec
15.7 sec
536 ms
Visit templines.com now to see the best up-to-date Templines content for Turkey and also check out these interesting facts you probably never knew about templines.com
Affordable, high-quality WordPress themes can easily be discovered with a little research, offering perfect themes for any professional, business, portfolio, or social networking site. No matter your ...
Visit templines.comWe analyzed Templines.com page load time and found that the first response time was 1.2 sec and then it took 16.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
templines.com performance score
name
value
score
weighting
Value11.0 s
0/100
10%
Value22.8 s
0/100
25%
Value22.5 s
0/100
10%
Value2,980 ms
3/100
30%
Value0
100/100
15%
Value39.0 s
0/100
10%
1196 ms
183 ms
92 ms
343 ms
530 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 84% of them (103 requests) were addressed to the original Templines.com, 9% (11 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (11.3 sec) belongs to the original domain Templines.com.
Page size can be reduced by 1.8 MB (61%)
3.0 MB
1.2 MB
In fact, the total size of Templines.com main page is 3.0 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. 65% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 59.9 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 59.9 kB or 84% of the original size.
Potential reduce by 27.4 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. Templines images are well optimized though.
Potential reduce by 898.9 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 898.9 kB or 72% of the original size.
Potential reduce by 846.0 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. Templines.com needs all CSS files to be minified and compressed as it can save up to 846.0 kB or 85% of the original size.
Number of requests can be reduced by 82 (80%)
102
20
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Templines. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 40 to 1 for CSS and as a result speed up the page load time.
templines.com
1196 ms
wp-emoji-release.min.js
183 ms
jquery-ui.css
92 ms
style.css
343 ms
dashicons.min.css
530 ms
desktop_style.css
342 ms
styles.css
345 ms
style.css
347 ms
widget-style.php
508 ms
form-style.php
595 ms
settings.css
515 ms
style.css
1398 ms
bootstrap.css
1756 ms
theme.css
718 ms
blog.css
738 ms
woocommerce.css
723 ms
no-responsive.css
756 ms
animate.css
890 ms
custom.css
889 ms
debugging.css
897 ms
stylesheet.css
917 ms
style.css
1046 ms
simple-line-icons.css
1047 ms
isotope.css
1055 ms
magnific-popup.css
1077 ms
prettyPhoto.css
1323 ms
jquery.bxslider.css
1327 ms
flexslider.css
1328 ms
smart-menu.css
1363 ms
loader.css
1496 ms
bio.css
1484 ms
hexagons.min.css
1492 ms
jquery.mmenu.css
1538 ms
jquery.mmenu.dragopen.css
1741 ms
dynamic-styles.php
1784 ms
tabs.css
2100 ms
tabstyles.css
2305 ms
css
99 ms
css
164 ms
font-awesome.min.css
98 ms
js_composer.css
2855 ms
jquery.js
2898 ms
jquery-migrate.min.js
1552 ms
front_end_script.js
1602 ms
public.js
1767 ms
jquery.themepunch.tools.min.js
2001 ms
jquery.themepunch.revolution.min.js
2179 ms
modernizr.js
1798 ms
jquery.themepunch.tools.min.js
2158 ms
jquery.themepunch.revolution.min.js
2275 ms
jquery.easing.min.js
1809 ms
jquery.easypiechart.js
1970 ms
core.min.js
2118 ms
datepicker.min.js
2100 ms
comment-reply.min.js
2016 ms
jquery.form.min.js
2159 ms
css
186 ms
scripts.js
3163 ms
add-to-cart.min.js
2138 ms
jquery.blockUI.min.js
2015 ms
woocommerce.min.js
2157 ms
jquery.cookie.min.js
2191 ms
cart-fragments.min.js
2172 ms
jquery-migrate-1.2.1.min.js
1926 ms
jquery-ui.min.js
2302 ms
bootstrap.min.js
1924 ms
cssua.min.js
2055 ms
jquery.mmenu.min.js
2029 ms
jquery.mmenu.dragopen.min.js
1944 ms
jquery.mmenu.fixedelements.min.js
1941 ms
waypoints.min.js
2704 ms
ios-orientationchange-fix.js
2512 ms
jquery.bxslider.min.js
2606 ms
jquery.flexslider-min.js
1867 ms
jquery.magnific-popup.js
2269 ms
jquery.prettyPhoto.js
1951 ms
isotope.pkgd.min.js
2127 ms
masonry.min.js
2112 ms
imagesloaded.pkgd.min.js
2111 ms
sly.min.js
1908 ms
events.js
1908 ms
bio.js
2113 ms
cbpFWTabs.js
1933 ms
js_composer_front.js
1783 ms
scripts.js
1783 ms
templines2.png
1264 ms
slide1.jpg
11299 ms
logo5.png
2915 ms
00_safe_preview1-300x300.jpg
2476 ms
00_preview2-300x300.jpg
1799 ms
7store-300x300.jpg
1694 ms
00_preview2-300x300.jpg
2167 ms
00_preview4-300x300.jpg
1797 ms
drupal-eve-300x263.jpg
2162 ms
trans-shop-300x263.jpg
2137 ms
cleanwp-300x263.jpg
3418 ms
IczWvq5y_Cwwv_rBjOtT0w.woff
578 ms
CcKI4k9un7TZVWzRVT-T8xsxEYwM7FgeyaSgU71cLG0.woff
798 ms
-_Ctzj9b56b8RgXW8FAriRsxEYwM7FgeyaSgU71cLG0.woff
526 ms
-_Ctzj9b56b8RgXW8FAriRsxEYwM7FgeyaSgU71cLG0.woff
871 ms
8KhZd3VQBtXTAznvKjw-kxsxEYwM7FgeyaSgU71cLG0.woff
757 ms
RJMlAoFXXQEzZoMSUteGWD8E0i7KZn-EPnyo3HZu7kw.woff
755 ms
xkvoNo9fC8O2RDydKj12bxsxEYwM7FgeyaSgU71cLG0.woff
915 ms
JbtMzqLaYbbbCL9X6EvaIxsxEYwM7FgeyaSgU71cLG0.woff
730 ms
JbtMzqLaYbbbCL9X6EvaIxsxEYwM7FgeyaSgU71cLG0.woff
868 ms
1ImRNPx4870-D9a1EBUdPBsxEYwM7FgeyaSgU71cLG0.woff
1044 ms
PKCRbVvRfd5n7BTjtGiFZBsxEYwM7FgeyaSgU71cLG0.woff
752 ms
ftbg1.jpg
532 ms
icomoon.ttf
3256 ms
montserrat-regular-webfont-webfont.woff
5406 ms
garden-templines-shop-300x263.jpg
3537 ms
bg-gray.png
2990 ms
watch.js
13 ms
raleway-bold-webfont-webfont.woff
5949 ms
raleway-medium-webfont.woff
4392 ms
lato-regular-webfont-webfont.woff
3533 ms
frame-product.png
3528 ms
freethemeinstall.png
3515 ms
templines.com
2591 ms
large_left.png
2255 ms
large_right.png
2472 ms
fontawesome-webfont.woff
257 ms
templines.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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
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
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.
templines.com 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
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
templines.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
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 Templines.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 Templines.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.
templines.com
Open Graph description is not detected on the main page of Templines. 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: