There are some additional features are added to SharePoint 2013 listed as :
Enterprise Content Management (ECM) : Many improvements have been made to ECM especially in the field of eDiscovery, which is the process of locating all document records that relate to a specific subject or legal case. You can also use Team Folders to consolidate content stored in SharePoint and Exchange.
Web Content Management (WCM) : In SharePoint 2013, the structure and navigation of a WCM site is defined by managed metadata terms. This approach is highly flexible and enables administrators to reorganize their entire Web site without moving any content.
Search : In SharePoint 2013 there is a single Search engine that combines the best features of the SharePoint and FAST search engines in SharePoint 2010. New configuration objects, such as Query Rules and Result Types allow administrators to customize result sets to an unprecedented level.
Client object model (CSOM) : The CSOM existed in SharePoint 2010 but has been greatly extended in SharePoint 2013 to enable.
Search : In SharePoint 2013 there is a single Search engine that combines the best features of the SharePoint and FAST search engines in SharePoint 2010. New configuration objects, such as Query Rules and Result Types allow administrators to customize result sets to an unprecedented level.
Client object model (CSOM) : The CSOM existed in SharePoint 2010 but has been greatly extended in SharePoint 2013 to enable.
Request Management : Administrators can use the Request Management feature to distribute Incoming requests across Web Front-End servers in the SharePoint farm. For example, they can use static weights to route more requests to a new, high specification server and thus take load off an older, slower server. You could also route all requests from a particular browser, such as IE9, through a specific server or deny requests from certain IP address ranges.
Shredded Storage: When users make changes to documents, SharePoint 2013 can apply those
Changes to the document in the content database without a full refresh of the whole document. If only a single change has been made to a large document, this can enormously reduce the quantity of data sent over the network and, if versioning is used, the volume of the content database.